Displaying 20 results from an estimated 7000 matches similar to: "Entering times around the start of daylight savings time"
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
2005 Oct 25
2
strptime problem for 2004-10-03 02:00:00
Hello, I at first thought this was a system or locale issue, but since
it occurs on
both Windows and Linux and only for 2004 (AFAIK) I report it.
I have a problem with as.POSIXct for the hour between
"2004-10-03 02:00:00 GMT" and "2004-10-03 02:59:59 GMT".
In short, the 2 AM (GMT) hour in 2004 (but not in other years) is
interpreted as 1 AM by strptime:
(I use ISOdatetime
2020 Oct 01
3
timezone tests and R-devel
The return value of Sys.time() today with a timezone of US/Eastern is
unchanged between 4.0.3-patched and devel, but on devel the following test
fails
all.equal(x, as.POSIXlt(x))
with
x = Sys.time()
This means that devel does not complete make tests (failure on
tests/reg-tests-2.R)
It is entirely possible that it is an error on my end, I use
export TZ="US/Eastern"
but I have been
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
>
2005 Feb 10
3
question about sorting POSIXt vector
Dear useRs,
How come the first attempt to sort a POSIXt vector fails (Error:
non-atomic type in greater), while the second succeeds? (Code inserted
below.) The documentation says that POSIXt is used to allow operations
such as subtraction, so I'd expect sorting to work. Is this perhaps an
OS issue? (I run R 2.0.1 on Win xp.)
Thank you,
b.
#------------code
test <- c("2005-02-08
2004 May 24
1
as.matrix.data.frame() in R 1.9.0 converts to character when it should (?) convert to numeric
Conversion of a data frame to a matrix using as.matrix() when a
column of the data frame is POSIXt and all other columns are numeric
has changed in R 1.9.0 from R 1.8.1. The new behavior issues a
warning message and converts to a character matrix. In R 1.8.1, such
an object was converted to a numeric matrix.
Here is an example.
#### R 1.9.0 ####
> foo <- data.frame(
2020 Oct 02
2
timezone tests and R-devel
Yes, the potential issue I see is that
make check
fails when I explicitly set TZ. However, I set it to be the same as what
the system reports when I login.
Details: The system (RHEL) I am working on has
$ strings /etc/localtime | tail -n 1
EST5EDT,M3.2.0,M11.1.0
$ date +%Z
EDT
$ echo $TZ
US/Eastern
On Fri, Oct 2, 2020 at 9:48 AM Sebastian Meyer <seb.meyer at fau.de> wrote:
> Thank
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
2006 Nov 23
2
converting from numeric to Date
Hi all,
I have a Date, that has been converted to a number that represent the
count of seconds since year 1970, how do i convert it to a date ?
Example :
>Limite_x<-c(1131408000,1163548800)
>is(limite_x)
[1] "numeric" "vector"
But these numbers are dates, did R provide something that give you the
date from this numeric vector ?
Thks all.
COMTE
2005 Nov 10
4
write.table read.table with Dates
I've found several similar issues with write.table/read.table
with Dates on this list, but trying to follow this advice I still
get an error.
First, I read in data from several files, constructing several date/time
columns using ISOdatetime
> str(Tall$Begin)
'POSIXct', format: chr [1:40114] "2005-10-02 00:00:00" "2005-10-02
00:00:00" ...
> length(Tall$Begin)
2004 May 27
2
axis.POSIXct: Datetime data and plotting
I've run into a problem with the datetime axis generated by axis.POSIXct. It appears a similar issue was discussed in October 2003 under the subject line "datetime data and plotting" (see https://stat.ethz.ch/pipermail/r-help/2003-October/039071.html), but I wasn't able to determine whether there is a straightforward solution.
The code below produces a graph with apparently
2012 Jan 20
2
Incorrect DateTime using ISOdatetime in R
Dear list,
I need to transform the DateTime of my GPS data from:
"666.1751" into "yyyy/mm/dd hh:mm:ss"
I have the following code:
d$Date <- ISOdatetime(2009, 1, 1, 0, 0, 0, tz = "GMT")+d$Date*(24*3600)
This gives me: 2010-10-29 04:12:09, which is wrong. It should be 2010-10-29
06:12:09
Another example:
418.3219 corresponds to: 2010-02-23 07:43:30, but it
2005 Nov 07
1
New Standard/Daylight time-change dates in rhel4u2 butnot centos4.2?
Which is why I always symlink /etc/localtime Not only does it solve
these issues, but it makes it very clear which timezone is selected!
-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Aleksandar Milivojevic
Sent: Monday, November 07, 2005 2:45 PM
To: centos at centos.org
Subject: Re: [CentOS] New Standard/Daylight time-change
2009 Jul 02
1
help exporting to excel via xlsReadWritePro
I’m trying to export a file from R to excel using the xlsReadWritePro function and I keep getting the error below. I get the same error when I use the oledatetime function. My current date format is mm/dd/yyyy, which is how I want it in excel. Also is there anyway to export different datasets to multiple sheets similar to the ods function in SAS?
<?xml:namespace prefix = o ns =
2004 Mar 05
3
as.POSIXct problem
Hi all,
I'm having difficulty converting a 'dates' object to a POSIXct object:
testDATES<-c(35947,35971,36004,36008,36053,36066)
testDATES<-chron(dates=testDATES, format = c(dates = "m/d/y"),
origin=c(month = 12, day = 30, year = 1899))
>[1] 06/01/98 06/25/98 07/28/98 08/01/98 09/15/98 09/28/98
> as.POSIXct(testDATES)
[1] NA NA NA NA NA NA
2009 Jan 19
1
maptools, sunriset, POSIX timezones
Hi ...
I wonder if anyone can provide some insight into why the first three
examples using the sunriset function (appended below, with results) give
the correct answer, but the fourth generates and error.
The first two use ISOdatetime with and without a time zone attribute,
and the sunriset function returns the correct sunset time.
The third and fourth adds 10 seconds to the ISOdatetime
2002 Apr 08
1
Problem(?) in strptime()
I think the following examples illustrate the crux of the matter
(version and OS info are below).
The problem has to do with the transition from standard time to
daylight savings time. My timezone, US/Pacific, has two parts:
standard time (PST) 8 hours behind GMT and daylight savings time
(PDT) 7 hours behind GMT. The transition takes place this year on 7
April at 02:00, when 02:00 is
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
2005 Aug 27
2
zoo, zooreg, & ISOdatetime
I create a zooreg object that runs from Jan-1-2002 0:00 to Jun-1-2005
0:00...
regts.start = ISOdatetime(2002, 1, 1, hour=0, min=0, sec=0, tz="")
regts.end = ISOdatetime(2005, 6, 1, hour=0, min=0, sec=0, tz="")
regts.zoo <- zooreg( NA, regts.start, regts.end, deltat=3600 )
Upon inspection:
> regts.zoo[1:3]
2002-01-01 00:00:00 2002-01-01 01:00:00 2002-01-01 02:00:00
2009 Feb 10
3
ISOdatetime gives NA for a specific date
Hi all,
I am using ISOdatetime, and I just found out that when I do
ISOdatetime(1995,03,26,2,10,0) (or any other value under minutes or seconds)
I get NA
This does not happen with the same time in other dates, nor with different
hours in the same date.
Any hint why this happens?
Using R 2.8.1 under ESS/GnuEmacs under Windows XP
Pedro
--
View this message in context: