Re: [R] seq() problem with chron

2018-09-06 Thread Jeff Newmiller
See FAQ 7.31... chron uses floating point representation, and there is some error accumulating. I also think there may be at least one bug in chron::seq.dates(), but I think POSIXct is significantly better than chron anywway so I don't intend to debug chron. # # wit

Re: [R] seq() problem with chron

2018-09-06 Thread Daniel Nordlund
On 9/5/2018 10:00 PM, Waichler, Scott R wrote: Hi, I encountered the problem below where the last value in the chron vector created with seq() should have a time of 15:30, but instead has 15:15. What causes this and how can I make sure that the last value in the chron vector is the same as th

[R] seq() problem with chron

2018-09-05 Thread Waichler, Scott R
Hi, I encountered the problem below where the last value in the chron vector created with seq() should have a time of 15:30, but instead has 15:15. What causes this and how can I make sure that the last value in the chron vector is the same as the "to" value in seq()? library(chron) dt1 <- c