search

HalfEatenPie / hydrosanity

Automatically exported from code.google.com/p/hydrosanity
http://code.google.com/p/hydrosanity
0 stars 0 forks source link

use zoo objects #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
need a more standard time series format.

zoo is pretty standard, and can handle irregular and regular series. can be
coerced to ts.

need to handle intersect / union of multiple time series.

need to handle quality codes - store as numeric and convert to factor when
needed?

how to keep quality codes with multiple time series? can't do it unless
store series separately.

need to adapt for representing time periods - end() / window()

Original issue reported on code.google.com by foolish.android on 31 Jul 2007 at 2:02

GoogleCodeExporter commented 9 years ago 
really need to do this. all my utility functions work with "timeblob" objects, 
but
when working with multiple synchronised series, they are transformed to data 
frames.
it does not make sense to reproduce, maintain and document so much 
functionality...
particularly since hydrosanity is supposed to have pedagogical value, so should 
use
standard objects and methods.

use a simple function to extract quality codes, like Gabor's toDF. get column 
"Qual"
and use a constant set of a levels (be sure to not ever drop levels!).

Original comment by foolish.android on 4 Sep 2007 at 2:07