From: Brian Beckage <[EMAIL PROTECTED]>
>
> Thanks to all who responded to my posting.
>
> At 11:39 AM -0500 11/12/03, Gabor Grothendieck wrote:
> >You are being hit by a timezone problem. Its not really shifting
> >the days by one. Its working in the GMT timezone, not yours.
> >
> >If you can
as chron or
an alternative, should be in the base to encourage wider use.
I agree. Thanks again for your help.
Brian
---
Date: Wed, 12 Nov 2003 10:05:39 -0500
From: Brian Beckage <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [R] Chron, as.POSIXct problem
Dear R list,
I noti
n-timezone) time such as chron or
an alternative, should be in the base to encourage wider use.
---
Date: Wed, 12 Nov 2003 10:05:39 -0500
From: Brian Beckage <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [R] Chron, as.POSIXct problem
Dear R list,
I noticed the following
Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> Does not happen on Solaris or Linux, so looks like a MacOS X problem.
It does not happen on my Mac G4 box (R 1.8.0 on MacOSX 10.2.6).
--Philippe
> Here is some crosschecks:
>
> > unclass(datesTest)
> [1] -6301 -6300 -6299
> attr(,"format")
> [1
Does not happen on Solaris or Linux, so looks like a MacOS X problem.
Here is some crosschecks:
> unclass(datesTest)
[1] -6301 -6300 -6299
attr(,"format")
[1] "m/d/y"
attr(,"origin")
month day year
1 1 1970
> unclass(as.POSIXct(datesTest))
[1] -544406400 -54432 -544233600
On Wed
Dear R list,
I noticed the following 'problem' when changing the format of dates
created with seq.dates() (from the Chron library) using as.POSIXct()
(R 1.8.0 on OSX 10.2.8):
datesTest<-seq.dates(from="10/01/1952", length=3, by="days");
datesTest
[1] 10/01/52 10/02/52 10/03/52
# Now changing
