[SciPy-User] failing to create a scikit.timeseries object
Thu Jun 3 02:36:08 CDT 2010
I Thank you all and I apologize for my very bad code snippet.
Do you know whether in scikits.timeseries there is a command / option /
configuration that allows to store time using long instead of integer?
Probably it might be necessary also to setup a callback somewhere able to
convert the datetime into this internally stored number ; have you any idea
On Wed, Jun 2, 2010 at 9:50 PM, Pierre GM <firstname.lastname@example.org> wrote:
> On Jun 2, 2010, at 3:03 PM, Robert Ferrell wrote:
> > I think that second resolution is the highest frequency available (at
> least that's what I see in the documentation).
> > Here's how to make a date array:
> > ts.date_array(freq='S', dlist=d)
> > DateArray([01-Jan-2010 10:10:02, 01-Jan-2010 10:10:02],
> > freq='S')
> > I don't know if timeseries Date objects can resolve microsecond
> It shouldn't. Internally, dates are stored as integers. The difference
> between one frequency and another is the reference used to convert integers
> back to some dates (eg., with an "ANN" frequency, we just store the year;
> with a "MON" freq, we just store the nb of months since 01/01/01...).
> Because so far the highest frequency is "SEC", there's no way to distinguish
> times at a larger frequency.
> SciPy-User mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-User