similar to: Buglet in handling times in R-3.5.1

Dear R developers, I have found a minute bug in R-3.5.1 (Windows version), about how times not an exact number of seconds are displayed. > as.POSIXct("1969-01-01 01:00")+0.3 [1] "1969-01-01 01:00:01 CET" > as.POSIXct("1970-01-01 01:00")+0.3 [1] "1970-01-01 01:00:00 CET" So for 1969, adding 0.3 of a second means you round UP, for 1970 you round DOWN.

The max argument of print.default() does not override options(max.print), see below. R 3.5.1 and R-devel both seem good. G?bor > options(max.print = 1) > print(data.frame(a=1:10)) a 1 1 [ reached 'max' / getOption("max.print") -- omitted 9 rows ] > print(data.frame(a=1:10), max = 100) a 1 1 [ reached getOption("max.print") -- omitted 9 rows ] >

https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16660 Here is the bug, which R.home may generate a path contains a whitespace. this will cause Rcpp failed executing sourceCpp > sourceCpp("b:/2018-12-14/src/18020/MCMC.cpp") Error in system(cmd, intern = !showOutput) : 'D:/Program' not found Error in system(cmd, ignore.stderr = TRUE, intern = TRUE) :

function ppois is a function calculate the CDF of Poisson distribution, it should generate a non-decreasing result, but what I got is: > any(diff(ppois(0:19,lambda=0.9))<0) [1] TRUE Actually, > ppois(19,lambda=0.9)<ppois(18,lambda=0.9) [1] TRUE Which could not be TRUE. Code is tested in both R 3.5.1 and Microsoft R Open 3.5.1. _

FWIW I can reproduce on macOS with R 3.5.1. A smaller example: system2("ls", timeout = 5); x <- sample(1:1E8) If I try to interrupt R while that sample call is running, R itself is closed. Best, Kevin On Fri, Sep 14, 2018 at 10:53 AM Emil Bode <emil.bode at dans.knaw.nl> wrote: > > I hope it's not too specific in my setup... > I've tried with system2

I can't reproduce this. Can you be more precise: exactly where are you putting the system2 call and exactly where are you sending the interrupt signal with ^C? Best, luke On Fri, 14 Sep 2018, Emil Bode wrote: > Hi all, > > I found some strange behaviour, which I think is a bug. Could someone make an account for me on Bugzilla or pass on my report? > > The problem: > When

Not in print.default(), but in print.data.frame(), which is now doing its own max= handling but not passing max to print.default (maechler, r75122 --- was this really for r-patched? -pd > On 22 Sep 2018, at 23:46 , G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > The max argument of print.default() does not override > options(max.print), see below. > R 3.5.1 and R-devel

Hi all, I found some strange behaviour, which I think is a bug. Could someone make an account for me on Bugzilla or pass on my report? The problem: When pressing Ctrl-C when a file is sourced in R, run from Terminal (macOS), sometimes the entire session is ended right away, while I just want to stop the script. This is the case when I press Ctrl-C while some functions are running that don?t

R-devel: Some very inconsistent behavior, that I can't seem to find documented. Sys.setenv(TZ="GMT") str(unclass(strptime("1969-12-31 23:59:59","%Y-%m-%d %H:%M:%S"))) List of 9 $ sec : num 59 $ min : int 59 $ hour : int 23 $ mday : int 31 $ mon : int 11 $ year : int 69 $ wday : int 3 $ yday : int 364 $ isdst: int 0 - attr(*, "tzone")= chr

I hope it's not too specific in my setup... I've tried with system2 added on the first line, so: Example.R: system2('ls', timeout=5) cat('Start non-interruptable functions\n') sample_a <- sample(1:1e7) sample_b <- sample(1:2e7) matching <- match(sample_a, sample_b) cat('Finished\n') Sys.sleep(10) And in terminal/bash: R --vanilla

Full_Name: Arni Magnusson Version: 1.6.2 OS: Windows XP Submission from: (NULL) (210.48.49.68) Hi there. I'm experiencing unexpected behaviour from as.POSIXct: > as.POSIXct("1969-12-24") [1] "1969-12-23 23:00:00 New Zealand Standard Time" > as.POSIXlt("1969-12-24") [1] "1969-12-24" > as.POSIXlt("1969-12-24")+1 [1] "1969-12-23

A user here noticed the following difference between Linux and Windows versions of R-2.15.3 (and R-3.0.0, I think) when using times within a second of the end of 1969: f <- function (sec = -1) { x1 <- as.POSIXct(c(2 * sec, sec, 0), origin = "1970-01-01", tz = "UTC") x2 <- as.POSIXlt(x1) x3 <- as.POSIXct(x2, origin = "1970-01-01", tz =

>>>>> Emil Bode >>>>> on Tue, 12 Jun 2018 12:00:42 +0000 writes: > I agree that calling it invalid is a bit confusing, but I?m not sure what the wording should be, as the problem is that the conversion to POSIXlt is failing. > The best solution would be to extend the whole POSIXlt-class, but that?s too much work. > I?ve done some experiments, and it

>>>>> Tim Taylor >>>>> on Thu, 6 Jul 2023 15:11:41 +0100 writes: > Ah yes ... and reading the as.data.frame help we see (emphasis mine): > "... Direct calls to as.data.frame.<class>() are still possible (*base > package!*), for 12 atomic base classes, but will deprecated ..." > So it does seem that a lot of these

> x<-as.POSIXct("1970-1-1", tz="UTC")-.5 > y<-as.POSIXct("1970-1-1", tz="UTC")+.5 > x==y [1] FALSE # of course but x and y "appear" to be the same when formatted, even with extra precision: > format(x, format="%Y-%m-%d %H:%M:%OS2") [1] "1970-01-01 00:00:00.50" > format(y, format="%Y-%m-%d

Dear list: working with date/times I have come across a problem that ISOdate and ISOdatetime are too slow on large vectors of data. I was surprised just until I looked at the implementation and the man page: "ISOdatetime and ISOdate are convenience wrappers for strptime". In other terms, they convert data to character representation first in order to create a POSIXlt object that is then

Hello! After posting this a version of this on r-help, Bert Gunter kindly suggested I should also post it here. Apologies for any cross-posting which may occur. My thanks to Jeff Newmiller and Marc Schwartz for setting me straight on one or two matters. If you're a newly-minted (pun _fully_ intended) user of Linux Mint 19 ("Tara") and you find you're having issues installing R

From:r-devel-admin@stat.math.ethz.ch on 02/22/2003 12:00 PM CET Sent by: r-devel-admin@stat.math.ethz.ch Please respond to r-devel@stat.math.ethz.ch To: r-devel@stat.math.ethz.ch cc: (bcc: Asheka Rahman/arahma1/LSU) Subject: R-devel digest, Vol 1 #101 - 10 msgs Send R-devel mailing list submissions to r-devel@stat.math.ethz.ch To subscribe or unsubscribe via the World Wide Web,

I'm having difficulties with daylight saving times in US time zones. (Apologies for the long post, but the problem seems subtle and complex, unless I'm doing something completely wrong, in which case it should be evident from the first 10 lines below.) This is what I see, using a (slightly modified) example from ?as.POSIXlt : > as.POSIXlt((d <- Sys.time()), "EST5EDT") #

Moving on from the discussion of the fact that length(x)==9 for any POSIXlt object x (which seems diabolically confusing, given that 'c' and '[' are defined for POSIXlt and have the vector-like behavior one would expect), what about having some guidelines for coding and documentation of vector-like classes? (1) a vector-like class should implement functions in groups: