search for: usetz

...that *printing* the unusual POSIXct Jskud> value is suspect. that's correct. Jskud> value is suspect. Looking at a R-1.8.1 install, we Jskud> find these definitions in base/R/base: Jskud> print.POSIXct <- function(x, ...) { Jskud> print(format(x, usetz=TRUE), ...) invisible(x) } Jskud> print.POSIXlt <- function(x, ...) { Jskud> print(format(x, usetz=TRUE), ...) invisible(x) } Jskud> However, looking at the 2.1.0 src file Jskud> R-2.1.0/src/library/base/R/datetime.R, we find Jskud> print.POSIXct...

...Attaching package: ?lubridate? The following object is masked from ?package:base?: date Warning message: package ?lubridate? was built under R version 3.4.0 *** caught segfault *** address (nil), cause 'unknown' Traceback: 1: format.POSIXlt(x, usetz = TRUE) 2: format(x, usetz = TRUE) 3: print(format(x, usetz = TRUE), ...) 4: print.POSIXlt(x) 5: function (x, ...) UseMethod("print")(x) Possible actions: ... Hope I'm not doing something illegal... Thanks, Frederick

...ary/base/R/datetime.R around line 234 looks like the ... argument is passed to print, not to format. print.POSIXct <- print.POSIXlt <- function(x, ...) { max.print <- getOption("max.print", 9999L) if(max.print < length(x)) { print(format(x[seq_len(max.print)], usetz = TRUE), ...) cat(' [ reached getOption("max.print") -- omitted', length(x) - max.print, 'entries ]\n') } else print(if(length(x)) format(x, usetz = TRUE) else paste(class(x)[1L], "of length 0"), ...) invisible(x) } T...

..., rho=0x8ade530, callrho=0x8ade530, defrho=0x829d4c0, ans=0xbff14cb8) at objects.c:328 So it would seem that *printing* the unusual POSIXct value is suspect. Looking at a R-1.8.1 install, we find these definitions in base/R/base: print.POSIXct <- function(x, ...) { print(format(x, usetz=TRUE), ...) invisible(x) } print.POSIXlt <- function(x, ...) { print(format(x, usetz=TRUE), ...) invisible(x) } However, looking at the 2.1.0 src file R-2.1.0/src/library/base/R/datetime.R, we find print.POSIXct <- function(x, ...) { print(format(x, usetz=TRUE,...

1) Why did you submit this *twice*, as PR#7826 and PR#7827? Please don't be so careless of the volunteers' time. 2) > print.POSIXct function (x, ...) { print(format(x, usetz = TRUE, ...), ...) invisible(x) } is definitely *not* implicated. (Use of ... in two places is correct.) 3) On FC3: > unusual_and_faults Error: protect(): protection stack overflow > format(unusual_and_faults) Error: protect(): protection stack overflow > as.POSIXlt(unusual_and_fa...

...;m struggling with time zone version when expressed as hours offset from GMT. Can anyone confirm that the behaviour below is incorrect? It seems that the GMT offsets are backwards: > format(as.POSIXct("2011-05-23 17:23:00", tz="Europe/London"),tz="America/New_York",usetz=T) [1] "2011-05-23 12:23:00 EDT" - this works. > format(as.POSIXct("2011-05-23 17:23:00",tz="GMT"),tz="GMT-5",usetz=T) [1] "2011-05-23 22:23:00 GMT" - this doesn't work: 17:23:00 GMT should be 12:23:00 GMT-5! Thanks. R version 2.13.0 (...

...oks like the ... argument is passed to print, not to > format. > > print.POSIXct <- > print.POSIXlt <- function(x, ...) > { > max.print <- getOption("max.print", 9999L) > if(max.print < length(x)) { > print(format(x[seq_len(max.print)], usetz = TRUE), ...) > cat(' [ reached getOption("max.print") -- omitted', > length(x) - max.print, 'entries ]\n') > } else print(if(length(x)) format(x, usetz = TRUE) > else paste(class(x)[1L], "of length 0"), ...) &...

...rptime(x='2007-09-22', format='%Y-%m-%d')) > strftime(x=foo, format='%Y-%m-%d') Error in strftime(x = foo, format = "%Y-%m-%d") : wrong class It's pretty clear why, given the first two lines of the function: > strftime function (x, format = "", usetz = FALSE, ...) { if (!inherits(x, "POSIXlt")) stop("wrong class") if (format == "") { times <- unlist(unclass(x)[1:3]) secs <- x$sec secs <- secs[!is.na(secs)] np <- getOption("digits.secs") i...

...; So it would seem that *printing* the unusual POSIXct value is suspect. > > Pretty obviously, yes. > > > Looking at a R-1.8.1 install, we find these definitions in base/R/base: > > > > print.POSIXct <- function(x, ...) > > { > > print(format(x, usetz=TRUE), ...) > > invisible(x) > > } > > > > print.POSIXlt <- function(x, ...) > > { > > print(format(x, usetz=TRUE), ...) > > invisible(x) > > } > > > > However, looking at the 2.1.0 src file > > R-2.1.0/src/li...

..., rho=0x8ade530, callrho=0x8ade530, defrho=0x829d4c0, ans=0xbff14cb8) at objects.c:328 So it would seem that *printing* the unusual POSIXct value is suspect. Looking at a R-1.8.1 install, we find these definitions in base/R/base: print.POSIXct <- function(x, ...) { print(format(x, usetz=TRUE), ...) invisible(x) } print.POSIXlt <- function(x, ...) { print(format(x, usetz=TRUE), ...) invisible(x) } However, looking at the 2.1.0 src file R-2.1.0/src/library/base/R/datetime.R, we find print.POSIXct <- function(x, ...) { print(format(x, usetz=TRUE,...

...),'%H:%M %Z') > [1] "09:12 PST" > > > On Mac OS X, however, > > R 2.0.1 Patched 2005-01-19 > >> Sys.time() > [1] "2005-01-19 09:18:27 PST" >> format(Sys.time(),'%H:%M %Z') > [1] "09:18 P" The man pages says: usetz: logical. Should the timezone be appended to the output? This is used in printing time, and as a workaround for problems with using '"%Z"' on most Linux systems. so after reading that, you get the correct result: > format(Sys.time(),'%H:%M',use...

...") > TZ > "" > > Sys.putenv("TZ"="CDT6CST") > > Sys.getenv("TZ") > TZ > "CDT6CST" > > format(strptime("199308070150","%Y%m%d%H%M"), "%Y-%m-%d %H:%M:%S", > tz="GMT", usetz=TRUE) > [1] "1993-08-07 01:50:00" > > format(strptime("199308070150","%Y%m%d%H%M"), "%Y-%m-%d %H:%M:%S %Z", > tz="GMT", usetz=TRUE) > Segmentation fault > > > Not nice. And the bug is in glibc, not R (the segfault is in st...

...ing object is masked from ?package:base?: > > date > > Warning message: > package ?lubridate? was built under R version 3.4.0 > > *** caught segfault *** > address (nil), cause 'unknown' > > Traceback: > 1: format.POSIXlt(x, usetz = TRUE) > 2: format(x, usetz = TRUE) > 3: print(format(x, usetz = TRUE), ...) > 4: print.POSIXlt(x) > 5: function (x, ...) UseMethod("print")(x) > > Possible actions: > ... > > Hope I'm not doing something illegal... > You are....

...bject is masked from ?package:base?: > > date > > Warning message: > package ?lubridate? was built under R version 3.4.0 > > *** caught segfault *** > address (nil), cause 'unknown' > > Traceback: > 1: format.POSIXlt(x, usetz = TRUE) > 2: format(x, usetz = TRUE) > 3: print(format(x, usetz = TRUE), ...) > 4: print.POSIXlt(x) > 5: function (x, ...) UseMethod("print")(x) > > Possible actions: > ... > > Hope I'm not doing something illegal... > >...

...utes(t1) $names [1] "sec" "min" "hour" "mday" "mon" "year" "wday" "yday" "isdst" $class [1] "POSIXlt" "POSIXt" > > format(t1, format = "%Y-%m-%dT%H:%M:%OS%z") # usetz = TRUE) # no change on usetz [1] "1995-05-25T15:30:00Mitteleurop?ische Sommerzeit" > > # Is the : in offset the problem? > t3 <- strptime("1995-05-25T15:30:00+1000", format = "%Y-%m-%dT%H:%M:%S%z") > attributes(t3) $names [1] "sec" "min&...

...a month or so. Although infrequent, it always crashes at the same place and gives the same error info, like this: *** caught segfault *** address (nil), cause 'memory not mapped' Traceback: 1: as.POSIXlt.POSIXct(x, tz) 2: as.POSIXlt(x, tz) 3: format.POSIXlt(as.POSIXlt(x, tz), format, usetz, ...) 4: structure(format.POSIXlt(as.POSIXlt(x, tz), format, usetz, ...), names = names(x)) 5: format.POSIXct(Sys.time(), format = "%H%M") 6: format(Sys.time(), format = "%H%M") 7: format(Sys.time(), format = "%H%M") ? ? I looked into the dumped core with gdb, a...

...lab time bar foo 1 1 2012-10-28 02:00:00 0 2 2 2 2012-10-28 02:00:00 1 1 3 3 2012-10-28 02:00:00 2 0 Converting to numeric, casting and converting back works as expected, although the timezone is not visible, because print.data.frame() calls format.POSIXct() with, usetz = FALSE: y <- cast(lab*time1~text, data=df2, value="value") y$time1 <- as.POSIXct("1970-01-01 01:00") + as.numeric(y$time1) Can anyone suggest a more elegant solution? Best, Tobias

Hi, Is it possible to create a ts() object, whose data is daily based BUT measured only on working days? In other words, suppose I have a data set with 255 observations, measured from 29 June 1959 to 30 June 1960. How would I create such a data? I tried something like: ts(c(...), start(1959, 180)) but I'm not sure what to use for frequency. In other words I don't know how to

...error info, > > like this: > > > > *** caught segfault *** > > address (nil), cause 'memory not mapped' > > > > Traceback: > > 1: as.POSIXlt.POSIXct(x, tz) > > 2: as.POSIXlt(x, tz) > > 3: format.POSIXlt(as.POSIXlt(x, tz), format, usetz, ...) > > 4: structure(format.POSIXlt(as.POSIXlt(x, tz), format, usetz, ...), > > names = names(x)) > > 5: format.POSIXct(Sys.time(), format = "%H%M") > > 6: format(Sys.time(), format = "%H%M") > > 7: format(Sys.time(), format = "%H%...

...e MD5 (NEWS) = b0b43ac87a5b5858098da065966551af MD5 (R-3/R-3.2.4-revised.tar.gz) = 552b0c8088bab08ca4188797b919a58f The relevant NEWS file entry is BUG FIXES: ? format.POSIXlt() behaved wrongly, e.g., format(as.POSIXlt(paste0(1940:2000,"-01-01"), tz="CET"), usetz=TRUE) ended in two "CEST" time formats. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com