Re: [R] timezones

2003-08-03 Thread Prof Brian Ripley
The solution to all these problems is to use UTC. You can't select a `standard time' such as EST: that does not exist for half the year. The only `timezone' without DST that we can guarantee to be available is UTC. You seem to have misunderstandings about how to set (not convert to) UTC. On Thu

Re: [R] timezones

2003-08-03 Thread james . holtman
<[EMAIL PROTECTED]To: [EMAIL PROTECTED], > [EMAIL PROTECTED] Sent by: cc:

[R] Timezones

2003-08-03 Thread Gabor Grothendieck
Thanks to Jerome Asselin (jerome at hivnet.ubc.ca) and Patrick Connolly (p.connolly at hortresearch.co.nz) for your work on this problem. We collectively were able to find two bugs, made easier by using our three different machines over 3 different time zones. See the following for details: htt

Re: [R] timezones

2003-08-03 Thread Jerome Asselin
Hi Gabor, I believe I have an answer to your first two inquiries. Both have something to do with the daylight vs. standard times. If I understand correctly, "GMT" has only standard time. Consider this example. > (now <- Sys.time()) [1] "2003-08-01 15:03:38 PDT" > (now.gmt <- as.POSIXlt(now,tz

Re: [R] timezones

2003-08-03 Thread Jerome Asselin
I share your concerns regarding Problems 1 and 2. However, I am unable to provide help on those at this moment. As for Problem 3, an alternative for the time being would be to use another package such as chron or date, although it would be preferable to use the classes of the base package if p

[R] timezones

2003-07-30 Thread Gabor Grothendieck
I have some questions and comments on timezones. Problem 1. # get current time in current time zone > (now <- Sys.time()) [1] "2003-07-29 18:23:58 Eastern Daylight Time" # convert this to GMT > (now.gmt <- as.POSIXlt(now,tz="GMT")) [1] "2003-07-29 22:23:58 GMT" # take difference > now-now.gmt

Re: [R] Timezones

2003-03-06 Thread Adrian Trapletti
[EMAIL PROTECTED] wrote: > zdump manipulates its environment directly but is otherwise the same code. > Solaris and glibc define putenv slightly differently. There are > two lines like > > char buff[20]; > > in src/main/datetime.c, and if you change those to > > static char buff[2

Re: [R] Timezones

2003-03-06 Thread ripley
zdump manipulates its environment directly but is otherwise the same code. Solaris and glibc define putenv slightly differently. There are two lines like char buff[20]; in src/main/datetime.c, and if you change those to static char buff[200]; it should work (increasing the len

Re: [R] Timezones

2003-03-06 Thread ripley
It's a Linux issue. Solaris gives: > Sys.time() [1] "2003-03-06 08:27:23 GMT" > as.POSIXlt(Sys.time(), "HST") [1] "2003-03-05 22:27:40 HST" which looks right to me. Past experience suggests that Solaris's POSIX conformance is much better than glibc's. Since my RH7.2 box does it too, I will loo

[R] Timezones

2003-03-05 Thread Adrian Trapletti
Can anybody give me a hint why as.POSIXlt doesn't recognize the same timezones that zdump knows about (Linux Suse 8.1 and Suse 7.3)? Is there a workaround? R : Copyright 2002, The R Development Core Team Version 1.6.1 (2002-11-01) R is free software and comes with ABSOLUTELY NO WARRANTY. You are