similar to: A different error in sample()

I believe the word "truncated" is causing the confusion. 3 is "the next smallest integer" following 2.5. But it is not the truncation done by trunc(). Rewording to "rounding the next smallest integer" would get rid of that confusion imho. Cheers Joris On Wed, Sep 19, 2018 at 7:57 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > This may be a doc

Hi there, using cbind with a numeric and raw argument produces an incorrect result. I've posted some details below, kind regards, Mike. e.g. > cbind(0, as.raw(0)) [,1] [,2] [1,] 0 6.950136e-310 A longer example shows that the result is not a rounding error, is not consistent, and repeated applications get different results. > cbind(0, as.raw(1:10))

Seems ok on my system. Axis label size changes when cex.axis does. ## tested in the middle of another long session, so many additional packages are attached, including some personal packages not available elsewhere > sessionInfo() R version 3.5.1 (2018-07-02) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS High Sierra 10.13.6 Matrix products: default BLAS:

????? Plots produced using svg in R 3.5.1 under macOS 10.13.6 ignores cex.axis=2.? Consider the following: > plot(1:2, cex.axis=2) > svg('svg_ignores_cex.axis.svg') > plot(1:2, cex.axis=2) > dev.off() > sessionInfo() R version 3.5.1 (2018-07-02) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS High Sierra 10.13.6 Matrix products: default BLAS:

Thanks Brodie, that's some nice detective work. If someone wanted to grant me access to Bugzilla, I'll be happy to post the bug and patch there (with your permission Brodie?) and help this bug get fixed. Mike. On Tue., 25 Sep. 2018, 10:53 pm brodie gaslam, <brodie.gaslam at yahoo.com> wrote: > > > For what it's worth the following patch fixes that particular problem

On 06/09/2018 10:47, peter dalgaard wrote: > I think this needs to be taken off the bug repository and continued here. By now it seems pretty clear that this is not an R bug, but a local problem on Spencer's machine, likely connected to font configurations. Or even on R-sig-Mac. > I poked around a bit on the three Macs that I can access, and found that fc-match does different things,

Dear sirs, One gets unexpected `residuals` if one is not aware of the meaning of weights when a weight is set to zero and the outcome is one in the `binomial` family in a call to `glm.fit`. The reason is the following line from `binomial()$initialize` > y[weights == 0] <- 0 Here is an example: pval <- seq(.05, .95, length.out = 25) X <- log(pval / (1 - pval)) - 2 Y <- c( FALSE,

I think this needs to be taken off the bug repository and continued here. By now it seems pretty clear that this is not an R bug, but a local problem on Spencer's machine, likely connected to font configurations. I poked around a bit on the three Macs that I can access, and found that fc-match does different things, including throwing warnings, hanging and even crashing my old MB Air... One

For what it's worth the following patch fixes that particular problem on my system.? I have not checked very carefully to make sure this does not cause other problems, but at a high level it seems to make sense.? In this particular part of the code I believe `mode` is taken to be the highest type of "column" encountered by `ctype` and based on conditionals it can (I think) be up to

Hello, I encountered some unexpected behavior of unzip when using info-zip's unzip instead of R's internal program. Specifically, unzip("file.zip", list=TRUE, unzip=/usr/bin/unzip) produces incorrect output if the zip archive has filenames with spaces, and results in an error if the zip archive includes an archive comment or file comments. Here is some code to reproduce along

R 3.5.1 on Windows 7 The documentation for 'var' says: "These functions return 'NA' when there is only one observation (whereas S-PLUS has been returning 'NaN'), and fail if 'x' has length zero." The function 'sd' (based on 'var') has similar documentation. However, I get: var(numeric(0)) [1] NA rather than an error. Personally I

I am trying, without success, to compile a custom locale for the utf-8 character set. I have issued this command: localedef --no-archive -f UTF-8 -i /usr/share/i18n/locales/en_CA at yyyy-mmm-dd en_CA at yyyy-mmm-dd.utf8 which produces the requisite files without reporting an error but which none-the-less insists on using the iso-8859-1 charset: LC_ALL=en_CA at yyyy-mm-dd locale charmap

Hi, The following call: xyplot(incidence ~ year, melanoma, panel=panel.smooth) produces a blank plot region with an error message: Error using packet 1 plot.new has not been called yet > sessionInfo() R version 2.11.1 (2010-05-31) x86_64-pc-linux-gnu locale: [1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=C

Hi, I've begun to use the lme4 package, rather than nlme, for more flexibility during modelling, and running the examples in lmer I receive this error message: ---<---------------cut here---------------start-------------->--- R> (fm1 <- lmer(Reaction ~ Days + (Days|Subject), sleepstudy)) Error in printMer(object) : no slot of name "status" for this object of class

I saw it also on some of my Ubuntu builds, but the issue went away after a make clean/make, so maybe give that a try. Best, luke On Wed, 24 Apr 2024, Ben Bolker wrote: > I'm using bleeding-edge R-devel, so maybe my build is weird. Can anyone > else reproduce this? > > View() seems to crash on just about anything. > > View(1:3) > *** stack smashing detected ***:

Hello, Suppose we need a function that takes a POSIXct object and need to calculate the time difference between it and GMT time: gmtDiff <- function(time) { time.gmt <- as.POSIXct(format(time, tz="GMT")) time.plt <- as.POSIXlt(time) dlstime <- ifelse(time.plt$isdst > 0, 1, 0) timezone <- as.numeric(difftime(time, time.gmt, units="hours"))

Hi, x <- c(rep(1800000003L, 10000000), -rep(1200000002L, 15000000)) This is correct: > sum(as.double(x)) [1] 0 This is not: > sum(x) [1] 4996000 Returning NA (with a warning) would also be acceptable for the latter. That would make it consistent with cumsum(x): > cumsum(x)[length(x)] [1] NA Warning message: Integer overflow in 'cumsum'; use

Hi, I can't pinpoint exactly since what R version I first noticed this error, but are others seeing this? R> vignette("grid") R> sh: : command not found instead of having the vignette displayed in the proper viewer? This is with: R> sessionInfo() R version 2.9.2 (2009-08-24) x86_64-pc-linux-gnu locale:

Hi, After the latest update of r-cran-* packages in sid, I'm getting the following message on startup: During startup - Warning message: package 'lattice' was built under R version 2.9.2 and help may not work correctly I haven't found anything wrong with the package's functionality so far though. ---<--------------------cut

Hi, I'm getting a segmentation fault as follows: ---<--------------------cut here---------------start------------------->--- R> begt <- as.POSIXct(strptime("10/01/2009 06:00:00", format="%d/%m/%Y %H:%M:%S"), + tz="GMT") R> tser <- seq(begt, by=5, length.out=91000) R> tser.trunc <- format(tser) Error: segfault from C