similar to: convert to chron objects

Displaying 20 results from an estimated 20000 matches similar to: "convert to chron objects"

2008 Aug 01
1
chron objects: input/output
Hi list, I have some questions regarding 1) conversion of date + time characters to chron 2) formatting chron object printing Regarding (1), Gabor's Rnews 2004 4/1 article has been indispensible, but I often work with files where dates and times are contained in a single field. In this case, I would like to control input/output of chron objects when each observation of date and time is
2006 Sep 20
1
hours() in 'chron': output != input
I encountered surprising (to me, at least) behavior while using 'hours()' in package 'chron.' I will be grateful if someone can point out my error or provide an explanation and intuitive solution (I suppose I could convert chron to a character vector and use substring, but I deal mostly with newbies and kludgy approaches don't inspire much confidence). I used 2.3.0 to
2001 Oct 30
2
creating chron object aggregates (e.g. sums by day)
What is the recommended/optimal way to perform aggregates on data frames with chron objects? Here is an example: >raw.data 1 07/09/01 4000 2 07/09/01 2000 3 07/11/01 1000 4 07/13/01 800 5 07/13/01 700 6 07/16/01 600 7 07/17/01 500 I'm trying to construct a function that would first aggregate the data (second column) by day (grouping by the first column) according to a
2006 Jan 19
1
chron library: format.times, parse.format and h:m (PR#8507)
Due to the following lines in parse.format: else if (nf == 3) { sep <- "" fmt <- substring(format, first = 1:3, last = 1:3) } If a format code has 3 characters, it will not use a separator: > library(chron) > mytime = times('7:15:00') > format(mytime,'h:m') [1] "0715" - Phil Spector
2006 Nov 20
1
a little help needed plotting chron object
Hello there, Using R 2.4.0 on Solaris (Unix): I am trying to control the X axis range on a simple time of day plot. I made a test program (below) that gets file time stamp information from the files in the directory where R starts. The goal of the test program is to plot the time of day of file creation on an x axis that spans a user-specified range (like 12:00:00 to 15:00:00). If I allow
2004 May 12
1
convert.times in chron, error when 59 < seconds < 60 (PR#6878)
Full_Name: Dennis Wolf Version: 1.9.0 OS: Mac OS 10.3.3 Submission from: (NULL) (160.91.76.23) platform powerpc-apple-darwin6.8 arch powerpc os darwin6.8 system powerpc, darwin6.8 status major 1 minor 9.0 year 2004 month 04 day
2004 Aug 18
1
Fwd: strptime() problem? - Resolved
Hi Gabor and everybody; Thanks Gabor, with the alternative step you've told me the problem is resolved. Comparing the two procedures: Extract from the source 'character' data: > rain$ts[2039:2046] [1] "25/03/2000 22:00:00 UTC" "25/03/2000 23:00:00 UTC" [3] "26/03/2000 00:00:00 UTC" "26/03/2000 01:00:00 UTC" [5] "26/03/2000 02:00:00
2006 Jun 23
2
problem with hist() for 'times' objects from 'chron' package
Hello dear useRs and wizaRds, I encountered the following problem using the hist() method for the 'times' classes from package 'chron'. You should be able to recreate it using the code: library(chron) # pasted from chron help file (?chron) dts <- dates(c("02/27/92", "02/27/92", "01/14/92", "02/28/92", "02/01/92")) class(dts)
2005 Aug 02
1
cut.Date functionality for chron date/time objects
Hello, I've encountered the need to cut some chron objects of the form: R> mychron <- chron(sort(runif(10, 0, 10))) R> mychron [1] (01/01/70 16:36:20) (01/02/70 00:08:46) (01/03/70 16:54:49) [4] (01/04/70 06:45:00) (01/07/70 06:21:24) (01/07/70 18:28:44) [7] (01/08/70 00:47:05) (01/08/70 05:11:44) (01/10/70 01:07:53) [10] (01/10/70 17:46:53) into arbitrary (e.g. a given number
2005 May 17
2
cumsum on chron objects
Hi, Is there some alternative to cumsum for chron objects? I have data frames that contain some chron objects that look like this: DateTime 13/10/03 12:30:35 NA NA NA 15/10/03 16:30:05 NA NA ... and I've been trying to replace the NA's so that a date/time sequence is created starting with the preceding available value. Because the number of rows with NA's following each available
2004 Mar 01
6
Find out the day of week for a chron object?
I know that this is correct: library(chron) x = dates("01-03-04", format="d-m-y", out.format="day mon year") print(x) It gives me the string "01 Mar 2004" which is correct. I also know that I can say: print(day.of.week(3,1,2004)) in which case he says 1, for today is monday. My question is: How do I combine these two!? :-) I have a
2012 Feb 17
6
convert zoo object to "standard" R object so I can plot and output to csv file
Another newbie question I got the 1 minute spine interpolation and 15 mean aggregation working with many thanks to Gabor Grothendieck using Zoo functions. I got a tip from Hasan Diwan to look at xts but it seemed I would make better progress using code from Gabor. Now I'm having trouble plotting this zoo object. I'm thinking I want a function to "split" the zoo object back to
2011 Aug 30
3
having trouble extracting week from chron object
Running R 2.13.1 on Windows XP. I would like to get week of the year (1-52) for each date. library(chron) dts <- dates(c("02/27/92", "02/27/92", "01/14/92","02/28/92", "02/01/92")) dts dts.chron <- as.chron(dts) dts.chron class(dts.chron) # all of these component extractions work: months(dts.chron) weekdays(dts.chron) years(dts.chron)
2002 Oct 18
1
Chron problem with R 1.6.0 (PR#2181)
Full_Name: Rick Bilonick Version: 1.6.0 OS: Linux (RH 7.1) Submission from: (NULL) (12.4.226.1) Hi. I'm using Red Hat 7.1 Linux (Intel 586). I installed the 1.6.0 rpm. No problems were reported. When I tried to load the chron library: Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library "/usr/lib/R/library/chron/libs/chron.so":
2012 Jun 15
2
time zones and the chron to POSIXct conversion
Hey R folks, i found some strange (to me) behaviour with chron to POSIXct conversion. The two lines of code result in two different results, on ewith the correct time zone, one without: library(chron) as.POSIXct(chron('12/12/2000'), tz = 'UTC') as.POSIXlt(chron('12/12/2000'), tz = 'UTC') Only the code below would give me a POSIXct object with the correct time
2005 Jun 01
2
problem with chron scales in lattice
I can't get the scales parameter in xyplot of lattice to work as I expected. I'm using R-2.1.0 and lattice 0.11-8. There should be year labels from 1992 to 2004 for the x axis in the plot below, but instead only a few of them appear, and in the wrong spots, as if the coordinate system has changed after finishing with the panel function. library(chron) library(lattice) # vertical grid
2005 Nov 16
1
COM dates (was origin and "origin<-" in chron)
I was just looking for an easy way to convert between COM datetime and chron datetime (both ways.) I found examples on the list, but they involved origin. Does anyone have functions for converting COM datetime <-> chron datetimethat work "safely"? David L. Reiner > -----Original Message----- > From: Gabor Grothendieck [mailto:ggrothendieck@gmail.com] >
2011 Sep 16
1
Mystified - comparing chron times
I have two local variables: startTime and expectedStartTime. Both are chron related objects. When I look at the class for the objects I can see they are of class "times". When I print them to the console, they both read: "09:30:00" When I print them as.numeric(), they both read: 0.3958333 When I try and compare them: (as.numeric(startTime) == as.numeric(expectedStartTime)) it
2012 Nov 27
2
Some questions about chron package..
Hello, I have questions while reviewing "chron" package(e.g.,chron.R). 1. What is the differences between 3 kinds of function definition ? 1) "name" &lt;- function(... 2) 'name' &lt;- function(... 3) name &lt;- function(... Do you know Why author used various kinds of definitions ? Is there no functional differences between them ? 2. I
2006 Jul 14
2
chron vs. POSIX
Hi, One of the big decisions when writing code is how to handle dates and times. Gabor Grothendieck provided an excellent overview of the issue in his R News 4/1 (2004) article, and many users and developers are probably using it as a guide. The proposed guideline is to use the simplest class required; as Gabor put it "use Date if possible, otherwise use chron, and otherwise use