Thank you all for the great input.
Russell, your design I think will make the best framework - after all,
defining and registering a model is hardly more difficult than defining
each model in the settings. Plus, I'm realizing now that each *type* of
data may come with its own particular functio
On the model side, to facilitate a generic visualization layer, you could
also consider an abstract parent class where you standardize time series
information that isn't the data.
For my time series data, I have this:
https://github.com/jonathanmorgan/django_time_series
I built a few django ti
On Tue, Mar 11, 2014 at 11:42 PM, RLange wrote:
> I'm currently working on an app for browsing and visualizing time-series
> data. Each point of time-series data may be a mix of Strings, Floats, and
> Ints. In my current design, I have a separate model for each of my data
> types, and I have been
Like number 2 but a little more amenable to searching
https://github.com/bradjasper/django-jsonfield
On Tuesday, March 11, 2014 10:42:24 AM UTC-5, RLange wrote:
>
> I'm currently working on an app for browsing and visualizing time-series
> data. Each point of time-series data may be a mix of Str
Without knowing much about your specifics, I would suggest looking into
MongoDB. You'll have some of the issues in #2 and you obviously won't have
a generic app that people without Mongo can use but I'd at least look into
it before you go any further.
On Tuesday, March 11, 2014 8:42:24 AM UTC-7
I'm currently working on an app for browsing and visualizing time-series
data. Each point of time-series data may be a mix of Strings, Floats, and
Ints. In my current design, I have a separate model for each of my data
types, and I have been writing a new view for each one. In other words, my
a
6 matches
Mail list logo
