search for: dstdays

Hello, I'm trying to plot data that has gaps in the timeline because my data only has the business day in it. When I do a line plot I get the data and then a blank area where a line goes the tail of the last data point to the head of the next data point. Is there a way I can do a line plot where the gaps are not plotted? Thanks in advance, Brian > names(utildf) [1]

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 Time" "2004-03-30 GMT Daylight Time" > R.version _...

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

I recently called plot(x,y) where x was an array of POSIXct timestamps, and was pleasantly surprised that it produced a nice plot right out of the box: z <- as.POSIXct(c("2006-10-26 08:00:00 EDT","2007-10-25 12:00:00 EDT")) x <- seq(z[1],z[2],len=100) y <- 1:100 plot(x,y,type="l") The X axis had nice labels, one tick mark every other month. (Plotting on

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",

I am trying to extract only the winters (defined to be 01-Dec through 28-Feb) of daily data from 1948-2002. There are 90 days in each winter season. I wrote the following code to gather the winter dates into a single vector: DJF <- NULL for(year in 1949:1999) { temp.begin <- strptime(paste("01/12", year-1, sep="/"), "%d/%m/%Y") temp.end <-

Hi R-devel. I've noticed a couple of quirks in the current time/date axis functions (axis.Date, axis.POSIXct, and the equivalents in lattice). Looking at the code, it seems like a fairly ad-hoc approach, often using pretty() on components of the time. This is not always ideal - for example a one-hour interval gets cut into 10-minute chunks rather than the more natural 15-minute chunks (since

Hello all, After beating my head against the wall for a few hours, I give up. I have two problems. 1. If I use seq() to generate a POSIXct series that crosses a daylight savings to stardard time change I get two values for the first day of change. The time change is Nov 6,2011. The value for Nov 7 turns into 23:00 on Nov 6, thus two values for Nov 6. (see below) So I put a time value (noon)

Hi R-devel / R-core In the new pretty() methods for Date and POSIXct https://svn.r-project.org/R/trunk/src/library/grDevices/R/prettyDate.R there is currently a "pretty" time step listed as "15 DSTdays"... but this actually doesn't line up well with months. Much better to implement directly what this is trying to do: i.e. to have a "halfmonth" time step. This is just the union of two "monthly" sequences, one on the 1st of each month and another on the 15th of each mo...

Thanks for this clarification. I have learned in the meantime that it is necessary to be very careful when using all these POSIX things. As another example, here is something that made me scratch my head just yesterday: When I create a sequence of days that happens to start before and ends in daylight savings time, I seem to lose a day: > seq(from = strptime("20030329",

...ration of S3 methods in namespaces were broken if the S3 generic was converted into an S4 generic by setting an S4 method. o Title and copyright holder of the reference manual are now in sync with the citation() command. o The validation code for POSIXlt dates and hence seq(, by="DSTdays") now works for large mday values (not just those in -1000...1000). (PR#6212) o The print() method for data frames now copes with data frames containing arrays (other than matrices). o texi2dvi() and buildVignettes() use clean=FALSE as default because the option is not supported...

...ration of S3 methods in namespaces were broken if the S3 generic was converted into an S4 generic by setting an S4 method. o Title and copyright holder of the reference manual are now in sync with the citation() command. o The validation code for POSIXlt dates and hence seq(, by="DSTdays") now works for large mday values (not just those in -1000...1000). (PR#6212) o The print() method for data frames now copes with data frames containing arrays (other than matrices). o texi2dvi() and buildVignettes() use clean=FALSE as default because the option is not supported...

...ows methods when there are multiple methods with the same signature for the same generic (still not fully supported, but at least the user can see them). * sys.on.exit() is now always evaluated in the right frame. (From Lionel Henry.) * seq.POSIXt(*, by = "<n> DSTdays") now should work correctly in all cases and is faster. (PR#17342) * .C() when returning a logical vector now always maps values other than FALSE and NA to TRUE (as documented). * Subassignment with zero length vectors now coerces as documented (PR#17344). Fu...

...ows methods when there are multiple methods with the same signature for the same generic (still not fully supported, but at least the user can see them). * sys.on.exit() is now always evaluated in the right frame. (From Lionel Henry.) * seq.POSIXt(*, by = "<n> DSTdays") now should work correctly in all cases and is faster. (PR#17342) * .C() when returning a logical vector now always maps values other than FALSE and NA to TRUE (as documented). * Subassignment with zero length vectors now coerces as documented (PR#17344). Fu...

I've rolled up R-1.8.0.tgz a short while ago. This is a new version with major changes (see below). Notably, the Macintosh version for OS X has been substantially improved; the old Carbon interface is no longer being supported. Also notice that the underscore will no longer work as an assignment operator. There is also a bunch of new functions and an assortment of bugs have been fixed. You

I've rolled up R-1.8.0.tgz a short while ago. This is a new version with major changes (see below). Notably, the Macintosh version for OS X has been substantially improved; the old Carbon interface is no longer being supported. Also notice that the underscore will no longer work as an assignment operator. There is also a bunch of new functions and an assortment of bugs have been fixed. You