similar to: axis.POSIXct: Datetime data and plotting

Displaying 20 results from an estimated 8000 matches similar to: "axis.POSIXct: Datetime data and plotting"

2001 Jul 06
1
output of system() call not returned in Win98
On one machine running Win98 and R 1.2.2 this command works: system("command.com /c dir",show=T,invisible=T) On another machine also running Win98 and R 1.2.2 it does not. Nothing appears. On another machine running Win98 and R 1.3.0 it also does not work. Is this a known problem? Many thanks for any help. Nick Barrowman, Ph.D. Thomas C. Chalmers Centre for Systematic Reviews
2001 Jul 06
0
Summary: output of system() call not returned in Win98
A solution to my problem was kindly suggested by Roger Bivand, namely the list.files() function. Thanks also to Prof. Ripley. My original message: > On one machine running Win98 and R 1.2.2 this command works: > > system("command.com /c dir",show=T,invisible=T) > > On another machine also running Win98 and R 1.2.2 it does not. > Nothing appears. > > On
2006 Apr 17
1
Tick mark alignment for POSIXct data
I am using POSIXct objects to store my date/time information. If I am plotting less that 2 days worth of data, I get the correct tick marks on the x-axis which is showing the 'day HH:MM' and these line up with the data points. If the data spans more than 2 days, the tick marks are now off. In the data below, I am creating some sample data and plotting the points. I am in the Eastern
2007 Jul 31
1
POSIXct Formating Error (PR#9819)
To Whom It May Concern: The following appears to be a bug in the way POSIXct dates are formated. The example is forced, but occurs naturally when importing Excel type dates (where fractional part is fraction of a day) and small rounding errors result. As shown, looking at the POSIXct class, it looks as if both times are 16:11:03 (truncation) Looking at as.numeric.POSIXct, it looks as if
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 Sep 18
1
as.POSIXct(as.Date()) independent of timezone
Dear R users, I am struggling a bit with the converting dates to full POSIX timestamps, in particular, I would like to somehow force the timezone to be local, i.e. the output of as.POSIXct(as.Date("2008-07-01")) should always be equal to "2008-07-01 00:00:00", is that achievable ? I tried to set the origin and the timezone, neither of which seems to make a difference. On my Mac
2004 Aug 19
2
proposed change to [.POSIXct
R developers, The "tzone" attribute is stripped from a POSIXct object when the subscript command is called ("[.POISXct"). This results in dates being printed in the locale specific format after a subscript operation is applied to a POSIXct object which has cause several problems for me in the past. Here is an example of this problem under R 1.9.1: > x <-
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
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
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
2011 May 31
3
DateTime Math in R - POSIXct
Greetings - I'm battling POSIXct, as per the code below. My input is actually an XL file, but the weird results below correctly model what I am seeing in my program. Before I punt and use lubridate or timeDate, could anyone please help me understand why POSIXct forces my variable back to GMT? I suspect that I'm not properly coding the tzone value, but it does not throw an
2007 Nov 05
2
its does not recognize POSIXct w/ both time and Date?
Hello all, I'm getting much further with my time-series work, but still getting into some problems. I'm using POSIXct time format with both date and time. I'd like to use that in an its object but It seems its only processes the date part of the POSIX time stamps: BMU_its_data <- its(data[BMUindex,2-4],dates=data[BMUindex,1]) Error in `row.names<-.data.frame`(`*tmp*`,
2004 Mar 03
2
read.spss and time/date information
I don't use SPSS but following through on your detective work can provide the likely answer. First note that both date numbers are evenly divisible by the number of seconds in a day, i.e. 24*60*60. This suggests that these numbers are seconds since some origin. Since we know "2003/02/11" corresponds to 13264300800 we deduce that the origin must be spss.orig <-
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
2004 Mar 06
0
Summary: as.POSIXct
Suggestions from both Prof Brian Ripley and Gabor Grothendiec solved my problem. From Prof Ripley: >This is a problem of your OS: your example works on all of mine. > >Can't you change the origin in chron? If not, you should certainly be >able to do > >as.POSIXct(strptime(as.character(testDATES), "%m/%d/%y")) This still resulted in NA's on my system. >
2003 Aug 04
0
as.POSIXct Bug when used with POSIXlt arg and tz= arg (PR#3646)
Tracking down this bug was joint work with Jermoe Asselin (jerome at hivnet.ubc.ca) and Patrick Connolly (p.connolly at hortresearch.co.nz). We collectively were able to determine that this is a problem in both Windows 2000 and in Linux and by testing it in our three time zones that it seems to be daylight savings time related. Conversion of POSIXlt datetimes to POSIXct appears to have problems.
2003 Jul 31
4
timezones
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 Time difference of -5 hours Note that the difference
2004 Mar 22
2
Date operations
Hello: Thanks in advance for your time ? I am having a data.frame with one of the columns containing the weeks as follows. How can I do the following in the most efficient way ? 1. Find the minimum date ? 2. Find the maximum date ? 3. How do we sort based on ascending order the date ? An example as follows. Week 1-Jan-01 (<----- MIN DATE) 7-Jan-01 14-Jan-01 21-Feb-01 (<----- MAX DATE)
2003 Oct 17
7
datetime data and plotting
If I take the following simple data: YEAR MONTH DAY WEIGHT.KG 2003 10 6 1.2 2003 10 12 1.2 2003 10 16 1.3 and format the date data and plot it: dates <- strptime(paste(DAY,MONTH,YEAR),"%d%m%Y") plot(c(min(dates),max(dates)),c(0,max(WEIGHT.KG)), xlab="Date",ylab="Weight (kg)",type="n") lines(dates,WEIGHT.KG) points(dates,WEIGHT.KG) I find that the
2007 Mar 19
3
R4.1: seq.POSIXt, tz="AEST" (PR#9572)
Times from seq.POSIXt come out wrong in AEST timezone around Feb 29 every leap year before 1970 (on Windows XP). According to help(DateTimeClasses), this is handled by "our own C code". > x <- as.POSIXct("1968-02-27") # tz="AEST" > x.gmt <- as.POSIXct("1968-02-27", tz="GMT") > data.frame( GMT=seq(x.gmt, by="day",