jim holtman a écrit :
Depending on how you are using POSIXct, you accuracy is limited to the
microsecond level. It is stored as a floating point number with 54
bit of accuracy (~16 digits) and currently the number of seconds since
1/1/1970 is 10 digits, so with microseconds adding 6 more, you a
Depending on how you are using POSIXct, you accuracy is limited to the
microsecond level. It is stored as a floating point number with 54
bit of accuracy (~16 digits) and currently the number of seconds since
1/1/1970 is 10 digits, so with microseconds adding 6 more, you are at
the limit:
> x <-
Gabor Grothendieck a écrit :
zoo is independent of time and date class so it does not restrict your
choice of index class. POSIXct supports sub-microsecond accuracy.
See ?POSIXct . Simply using the number of microseconds since the
start of the experiment is another possibility.
On Sat, Feb 6,
zoo is independent of time and date class so it does not restrict your
choice of index class. POSIXct supports sub-microsecond accuracy.
See ?POSIXct . Simply using the number of microseconds since the
start of the experiment is another possibility.
On Sat, Feb 6, 2010 at 8:25 AM, Laurent Rhelp
Dear R-List,
I have the habit of using R for my data processing and I like to use
the power of the lattice package. Presently, I have to manage time
series. So, in order to work properly I want to discover the zoo package
and the related methods (since lattice can work with zoo class). But m
5 matches
Mail list logo