similar to: Daylight savings time and conversion to POSIXt (arghh!)

Displaying 20 results from an estimated 2000 matches similar to: "Daylight savings time and conversion to POSIXt (arghh!)"

2002 May 12
0
{round,trunc}.POSIXt and daylight savings time (PR#1543)
I have found what looks like a small problem in trunc.POSIXt() involving the transition to/from standard time and daylight savings time. Assuming my assessment is correct, I have a potential solution to offer. If a time in daylight savings time is rounded such that the rounded value is on the other side of the transition, the isdst element does not get changed accordingly. I have tested only
2002 Apr 08
1
Problem(?) in strptime() -- short version
I decided my earlier email on this topic was rather long and wordy; here's a condensed version. I am sitting at a Solaris computer in the US/Pacific timezone. I have a file of data having times that includes the following three values 2002-4-7 1:30:00 GMT 2002-4-7 2:30:00 GMT 2002-4-7 3:30:00 GMT I have not been able to find a way to correctly convert these to either of the POSIX
2010 Feb 01
1
Error with cut.POSIXt and daylight savings time switchover dates
The following code: cut(as.POSIXct("2009-11-01 04:00:00", tz="America/Los_Angeles"), "1 day") gives the error: Error in seq.int(0, to - from, by) : 'to' must be finite This is related to November 1st, 2009 being the switchover date from daylight savings time to standard time in the America/Los_Angeles time zone. In particular, in cut.POSIXt, the starting
2007 Jun 21
1
Result depends on order of factors in unbalanced designs (lme, anova)?
Dear R-Community! For example I have a study with 4 treatment groups (10 subjects per group) and 4 visits. Additionally, the gender is taken into account. I think - and hope this is a goog idea (!) - this data can be analysed using lme as below. In a balanced design everything is fine, but in an unbalanced design there are differences depending on fitting y~visit*treat*gender or
2004 Apr 29
1
Entering times around the start of daylight savings time
I'm having problems entering dates and times around when daylight savings time starts. If I type (on R 1.8.1 on Gentoo Linux) > ISOdatetime(2004,4,4,0:4,0,0,"GMT") [1] "2004-04-03 19:00:00 EST" "2004-04-03 20:00:00 EST" [3] "2004-04-03 22:00:00 EST" "2004-04-03 22:00:00 EST" [5] "2004-04-03 23:00:00 EST" Giving the times
2012 Jul 02
1
Undocumented behavior around daylight savings time?
Apologies for the intrusion. I am a lurker on list. I have been working to convert a digitized signal from a matlab file into R for analysis and other applications. R.matlab is working fine, and it is easy to convert the matlab date-time number (days since year 0) into R date-time numbers (seconds since 1970-01-01). Unfortunately, when I cast the R date-time number into POSIXct format it seems
2008 Nov 07
2
Unexpected behavior of clocktime related to daylight savings time
Colleagues, I submitted this several days ago and no one responded, so I am trying again, trying a different subject line: I just encountered some unexpected behavior of difftime in relationship to the change from daylight savings to standard time. My understanding is that DST and ST take effect at 2AM. However, the results below suggests that R (version 2.8.0 in OS X) implements the
2002 May 17
0
round.POSIXt gets certain values wrong
For certain values, round.POSIXt(tm,'day') does not round to midnight as documented. The reason is that trunc.POSIXt() does not adjust the value of the isdst element. Assuming my assessment of the reason is correct, I have a potential solution to offer. Additional discussion is in bug report #1543. -Don > x <- c(as.POSIXct('2001-4-1 3:15'),as.POSIXct('2001-5-2
2003 Jun 17
0
A 'pretty' function for POSIXt objects
I have written a set of functions for POSIXt objects that I would like to offer for consideration for use in base R. They augment and extend existing functions. Briefly, ## pretty.ct function(x,specs=pretty.ct.specs) ## round.ct function(x, tstr='1 min' ) ## axis.ct function(side,x,specs=NULL,...) ## parse.timeint function(dv) ## parse.tstr
2002 Mar 26
1
seq.POSIXt() with short time intervals
I was surprised when seq.POSIXt() returned a single value rather than a vector, from inputs that I thought were reasonable. Here's an example to illustrate: > t0 <- ISOdatetime(2002,6,24,0,0,10) ## expected a sequence of 16 times 1 second apart > seq.POSIXt(from=t0,to=t0+15,by='1 sec') [1] "2002-06-24 00:00:10 PDT" ## traces to this call >
2004 Mar 30
1
seq.POSIXt() bug not fixed in R 1.8.1 (PR#4558)
I am still experiencing problems with seq.POSIXt() missing off the last day of the series: > seq(as.POSIXct("2004-03-25"),as.POSIXct("2004-03-31"),by="DSTdays") [1] "2004-03-25 GMT Standard Time" "2004-03-26 GMT Standard Time" "2004-03-27 GMT Standard Time" [4] "2004-03-28 GMT Standard Time" "2004-03-29 GMT Daylight
2006 Mar 07
0
rsync huge files from cygwin to linux stalls - bug?
hi there i'm trying to backup a 3gig directory with about 100.000 files from a windows pc to a linux box with rsync but the process stalls (hangs). setting a "--timeout 60" shows me that the i/o stalls. doing the same with smaller directories works perfectly but the whole 100.000 files seem to be too much. the process hangs before the file list is done. rsync doesn't start
2010 Jul 18
3
Arghh, dovecot-2 and lda
I cannot seem to get exim/lda working... In my exim log i just see these 2010-07-18 11:51:08 1OaYOJ-0003Vn-2P == brandon at olypen.com R=router_pop T=dovecot_deliver defer (2): No such file or directory: failed to chdir to maildir:~/maildir:INDEX=~/maildir/dovecot-index Now I have all the debugging on as far as i can tell, and exim is obviously being returned some value from dovecot because it
2012 Sep 05
2
POSIXlt and daylight savings time
I have a data frame that contains dates, but when I use as.POSIXlt() I lose the hours on all records. I traced this down to a particuar hour which causes the issue... > as.POSIXlt('2004-10-31 02:00:00') [1] "2004-10-31" > as.POSIXlt('2004-10-31 03:00:00') [1] "2004-10-31 03:00:00" How do I tell as.POSIXlt() to ignore daylight savings and just convert to
2007 Jan 30
1
New daylight savings law
*Hi All, * I presume the upstream provider is aware of this??? I am in Indiana. Go figure. Jerry ** *---------------- * *New Federal Law?Springing Forward in March, Back in November* Months after Indiana passed the law that got it in step with the rest of the country, the federal government announced a major change in Daylight Saving Time. In Aug. 2005, Congress passed an energy bill that
2006 Jan 06
1
Daylight Savings Time unknown in R-2.2.1
Under R-2.2.1, a POSIXlt date created with "strptime" has an unknown Daylight Savings Time flag: > strptime(20051208, "%Y%m%d")$isdst [1] -1 This is true on both Linux (details below) and Windows. It did not occur under R-2.1.0. Any ideas? TIA! > Sys.getenv("TZ") TZ "" Version: platform = i686-pc-linux-gnu arch = i686 os = linux-gnu
2010 May 10
1
System neutral Daylight Savings Time response?
I'm searching for an r command that will notify me if I create a time that does not exist due to Daylight Savings Time. For example, if I run the following command on a windows machine > ISOdatetime(2010,03,14,2,10,0, tz = "") # My system time is set to the United States Central Time Zone [1] NA R returns NA, which is the behavior I want. However, if I run the same command on a
2007 Feb 25
0
Upcoming change in Daylight Savings Time
This message, hopfully, summarizes all the questions people may have about the change affecting when Daylight Savings Time begins and ends for various time zones which takes effect this year. NOTE: Before you decide this message does not effect you please bear in mind that the most critical file involved in all of this is /etc/localtime. That is the zoneinfo file your system will be using to
2008 Nov 03
0
Unexpected behavior of difftime in relationship to daylight savings time
Colleagues, I just encountered some unexpected behavior of difftime in relationship to the change from daylight savings to standard time. My understanding is that DST and ST take effect at 2AM. However, the code below suggests that R (version 2.8.0 in OS X) implements the change at 2:16AM: Expected: > > difftime("2008-11-02 02:01:00", "2008-11-02 00:59:00")
2008 Oct 26
0
daylight savings time difference with rspec?
Hi all, I wanted to check this with you. I have an rspec example that checks the correct expiration date set on an object. The expiration is set in the model with expires_on = Time.now + next_duration[phase] where next_duration can either be in units of seconds or n.days (should be the same thing). n can be 3, 7, 25, or 30 days. in my example I check an interval because the two events are not