similar to: lubridate 1.1.0

Please find below the package announcement for the R package lubridate available from cran. Thank you, Garrett Grolemund Rice University ##lubridate Date-time data can be frustrating to work with in R. R commands for date-times are generally unintuitive and change depending on the type of date-time object being used. Moreover, the methods we use with date-times must be robust to time zones,

Please find below the package announcement for the R package lubridate available from cran. Thank you, Garrett Grolemund Rice University ##lubridate Date-time data can be frustrating to work with in R. R commands for date-times are generally unintuitive and change depending on the type of date-time object being used. Moreover, the methods we use with date-times must be robust to time zones,

Version 2.2 of the lubridate package is now available. lubridate makes it easier to work with date-time data. For example, it provides: * simple functions to extract and modify components of a date-time, such as years, months, days, hours, minutes, and seconds: year(), month(), day(), ... * quick and easy functions to parse date-times: ymd(), dmy(), mdy(), ... * helper functions for handling

Version 2.2 of the lubridate package is now available. lubridate makes it easier to work with date-time data. For example, it provides: * simple functions to extract and modify components of a date-time, such as years, months, days, hours, minutes, and seconds: year(), month(), day(), ... * quick and easy functions to parse date-times: ymd(), dmy(), mdy(), ... * helper functions for handling

With newest R devel #sessionInfo() R Under development (unstable) (2012-01-10 r58085) Platform: amd64-portbld-freebsd10.0 (64-bit) locale: [1] de_DE.ISO8859-15/de_DE.ISO8859-15/de_DE.ISO8859-15/C/de_DE.ISO8859-15/de_DE.ISO8859-15 attached base packages: [1] stats graphics grDevices utils datasets methods base I get the following error when I try to build and install lubridate from

It took me some time to realize this annoying behavior was coming from lubridate. Perhaps this behavior is unexpected a result of cursory knowledge of it.... ## The expected behavior > sometimes=c(0,1,2,3)*60*60*24 > as.POSIXct( sometimes, origin='1970-01-01', tz='GMT') [1] "1970-01-01 GMT" "1970-01-02 GMT" "1970-01-03 GMT" "1970-01-04

I took a look at Hadley's lubridate which seems a very neat package, but i am having a small problem with  concatenating lubridates to build vectors of it. Namely when function c( )  is applied to lubridate seems to change time to a local timezone in this particular case changing the date to previous one.  > d<-ymd('20111231') > d [1] "2011-12-31 UTC" > c(d) [1]

Dear all, I wish to create a POSIXct variable from date and time variables using the ymd_hm function in package lubridate. In some cases data for time is missing, which causes a problem for ymd_hm. I wish to find a smooth way to handle this. # Some example data: x <- data.frame(date = c("2011-09-22", "2011-07-28"), time = c("15:00", NA)) x # paste date and

Buas y feliz año y decada nueva, compañeRos, Me estoy encontrando con un problema tonto que no consigo resolver. Explico, tengo un dato que necesito sacar en un documento con codigo on line y no me saca el resultado de consola. dato <- 2272.13 round(lubridate::seconds_to_period(seconds(dato))), 0) En consola me da: "37M 52S" Pero en el documento ```Rmarkdown + Duración total

Hello, I know how to increment a date by calendar date: ticker$ldate <- ticker$tdate + days(5) How do I increment it by business days only so that week-ends are not counted? So for example friday november 2 + 5days becomes friday november 9 & not wednesday nov 7. Thanks for your help. -- View this message in context:

Hiya, maybe there is a native R function for this and if so please let me know! I have 2 data.frames with start and end dates, they read in as strings and I am converting to POSIXct. How can I check for overlap? The end result ideally will be a single data.frame containing all the columns of the other two with rows where there were date overlaps.

Hello, I have a list of dates in which I am going use for a time series analysis. I want to break these dates up into 2 week intervals and count the number of times a date appears in this interval. For example from Nov. 19, 2000 to Dec 2 ,2000 with the data listed below I want to return Start_date Count2000/11/19 4 Date: 2000/11/20 2000/11/21 2000/11/19 2000/11/29 My first approach was toa

Hi R Helpers, I recently tried to take advantage of the ability to download all the tickers in the S&P 500 using the functionality of tidyquant, but it threw an error. For summary, the set of commands that I ran was library(tidyquant) tq_index_options() tq_index("SP500") sessionInfo() R feedback including error message and sessionInfo are provided below. Guidance would be

Hadley, Overall seems like a cool and potentially really idea. I do have some thoughts/feedback, which I've put in-line below On Thu, Aug 23, 2018 at 11:31 AM, Hadley Wickham <h.wickham at gmail.com> wrote: > > <snip> > > conflicted applies a few heuristics to minimise false positives (at the > cost of introducing a few false negatives). The overarching goal is

Dear Hadley, There's been some mails from you lately about packages on R-devel. I would argue that the appropriate list for that is R-pkg-devel, as I've been told myself not too long ago. People might get confused and think this is about a change to R itself, which it obviously is not. Kind regards Joris On Thu, Aug 23, 2018 at 8:32 PM Hadley Wickham <h.wickham at gmail.com>

First, some general comments: This sounds like a useful package. I would guess it has very little impact on runtime efficiency except when attaching a new package; have you checked that? I am not so sure about your heuristics. Can they be disabled, so the user is always forced to make the choice? Even when a function is intended to adhere to the superset principle, they don't always

OK, so the consensus is (1) One cannot make strptime accept ISO8601-compliant zone designators (2) The lubridate package can (3) Or one can hack away with regex. Lubridate it is, then. But I do regard strptime's inability to process ISO8601-compliant zone designators as a bug. On Mon, 6 Nov 2023 at 13:18, jim holtman <jholtman at gmail.com> wrote: > try using 'lubridate'

Thanks to all who replied. On Mon, 6 Nov 2023 at 18:37, Richard O'Keefe <raoknz at gmail.com> wrote: > OK, so the consensus is > (1) One cannot make strptime accept ISO8601-compliant zone designators > (2) The lubridate package can > (3) Or one can hack away with regex. > Lubridate it is, then. > > But I do regard strptime's inability to process

Hola, Otra forma, utilizando la función de intervalos y la que comprueba si otro intervalo se solapa del paquete "lubridate": #---------------------- library(lubridate) fe.chas <- data.frame( entra=c('2001-01-01','2001-06-01','2003-01-01') ,sale=c('2002-01-01','2002-06-01','2004-01-01') ) ref <-

>>>>> Richard O'Keefe >>>>> on Mon, 6 Nov 2023 18:37:34 +1300 writes: > Thanks to all who replied. On Mon, 6 Nov 2023 at 18:37, > Richard O'Keefe <raoknz at gmail.com> wrote: >> OK, so the consensus is (1) One cannot make strptime >> accept ISO8601-compliant zone designators (2) The >> lubridate package