search for: sgiannerini

Hi, This report deals with p-values coming from chisq.test using the simulate.p=TRUE option. The issue is numerical accuracy and was brought up in previous bug reports 3486 and 3896. The bug was considered fixed but apparently was only mostly fixed. Just the typical problem of two values that are mathematically equal not ending up numerically equivalent. Consider this series of three 2x2

This report follows the post http://tolstoy.newcastle.edu.au/R/e6/devel/09/03/0760.html where it is shown that quantile() and IQR() do not work as documented. In fact they do not check for numeric input even if the documentation says = : ?quantile x numeric vectors whose sample quantiles are wanted. Missing values are ignored. ?IQR x a numeric vector. > quantile(factor(1:9)) 0%

Dear all, following the thread http://tolstoy.newcastle.edu.au/R/e2/devel/07/09/4338.html regarding the bug in the partial autocorrelation function for multivariate time series. I have prepared a web page with patches and relevant information. http://www2.stat.unibo.it/giannerini/R/pacf.htm Please do not hesitate to contact me for further clarifications regards Simone --

Dear all, I am managing a departmental purchase of an Opteron based workstation/server for scientific computing on which we will be running R. The environment will probably be either Unix/Linux or Solaris and the amount of RAM will be 8-16Gb, depending on the number of processors. My main concerns are the following: 1. How much does R benefit from passing from one processor to two/four

According to ?parCapply: parRapply and parCapply always return a vector. This appears not to be the case in the following minimal reproducible example: > library(parallel) > nslaves <- 2 > cl <- makeCluster(nslaves) > X <- matrix(2,nrow=3,ncol=4) > X <- rbind(c(1,1,0,1),X) > tv <- parCapply(cl,X,FUN=function(x){ +

Dear list, I do not know what would be the 'correct' answer to the following but I think that they should return the same value to avoid potential problems and hard to debug errors. Regards, Simone --------------------------------------- > NCOL(NULL) [1] 1 > NROW(NULL) [1] 0 > sessionInfo() R version 4.3.1 RC (2023-06-08 r84523 ucrt) Platform: x86_64-w64-mingw32/x64 (64-bit)

Dear all, the number of significant digits in summary default is digits = max(3, getOption("digits") - 3) on my platform this results to be 4. The point is that if you have, say, integer data of magnitude greater than 10^3 the command summary will produce heavily rounded results. A simple example follow: > x <- c(123456,234567,345678) > x [1] 123456 234567 345678 >

Dear all, given two numeric vectors x and y, the ACF(x) at lag k is cor(x(t),x(t+k)) while the CCF(x,y) at lag k is cor(x(t),y(t-k)). See below for a simple example. > set.seed(1) > x <- rnorm(10) > y <- rnorm(10) > x [1] -0.6264538 0.1836433 -0.8356286 1.5952808 0.3295078 -0.8204684 0.4874291 0.7383247 0.5757814 -0.3053884 > y [1] 1.51178117 0.38984324

Dear all, switch() called with just the EXPR argument causes R to hang so that the only way to stop it is to kill R. Reproducible example: > switch(EXPR="a") the internal C subroutine behind switch is do_switch located in R/src/main/builtin.c For convenience I reproduce it below. ***************************************************************************** SEXP attribute_hidden

Dear all, I found the following behaviour > rf(5,Inf,Inf) [1] 1 1 1 1 1 but > qf(0.1,Inf,Inf) [1] NaN Warning messages: 1: In qf(0.1, Inf, Inf) : value out of range in 'lgamma' 2: In qf(p, df1, df2, lower.tail, log.p) : NaNs produced incidentally, > pf(1.00000000000001,Inf,Inf) [1] 1 > pf(1.0000000000000001,Inf,Inf) [1] 0.5 Is this the expected behaviour? Thanks

Dear all, I am currently trying to create a package wrapping Fortran90 code, the RRTMG radiative transfer model( http://rtweb.aer.com/rrtm_frame.html). I am doing this on a Linux workstation, with gcc/gfortran, in case this matters. The code heavily relies on F90 features, in particular modules, which seem to clash with R's assumptions for calling compiled code. What I have done: -compiled

Thanks Tomas, I confirm the R Under development (unstable) (2018-04-26 r74651) version works for Rscript when the file name has a space, and no arguments are specified. C:\>"C:\Program Files\R\R-devel\bin\x64\Rscript.exe" "C:\foo bar.R" R Under development (unstable) (2018-04-26 r74651) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 7 x64 (build 7601)

Dear All, I found the following under R 2.3.0 on WINXP (tested on 2 PCs, I do not have access to the to Linux from this PC, sorry ... ) > set.seed(10) > x <- ts(rnorm(6),frequency=7) > x Time Series: Start = c(1, 1) End = c(1, 6) Frequency = 7 [1] 0.01874617 -0.18425254 -1.37133055 -0.59916772 0.29454513 0.38979430 > x[24] <- NA > x Time Series: Start = c(1, 1) End =

Dear all, I found the following on R 2.3.1. for Windows XPpro SP2, tested on 2 PCs AMD 64 3700+, Ati 9700 AMD Athlon 2400+, Matrox G550 Do the following: x <- as.matrix(0); fix(x) pasting a big chunk of data, for instance the one below, into a cell of the editor will crash the RGui. 333333333333333333 333333333333333333333333333 33333333333333333333333333333333333333333333

Dear all, following the thread http://tolstoy.newcastle.edu.au/R/e2/devel/07/09/4338.html regarding the bug in the partial autocorrelation function for multivariate time series. I have prepared a web page with patches and relevant information. http://www2.stat.unibo.it/giannerini/R/pacf.htm Please do not hesitate to contact me for further clarifications regards Simone --

Dear all, it looks like that tabulate() does not check for the bounds of the input. Reproducible example: > b <- 1:2 > tabulate(b[1:100]) [1] 1 1 > R.version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status Patched major 2 minor 11.1 year 2010 month 09 day

John, I had raised the matter ten years ago, and I was told that the topic was already very^3 old https://stat.ethz.ch/pipermail/r-devel/2006-September/042684.html there is some discussion on its origin and also a declaration of intents to change the default behaviour, which, unfortunately, remained a declaration. I agree that R could do better here, let's hope in less than ten years

Dear all, there seems to be a problem with displayed legends when a multiple figure environment is used, see the following example: par(mfrow=c(1,2)) curve(dnorm,col=4,from=-4,to=4); legend(-4,0.3,legend="curve",lty=1,col=4) legend(-4,0.2,legend="curve",lty=1,col=4) On my machines the first time the command legend() is issued the legend box stretches over the curve.

Dear all, it looks like fix() changes the class of mts objects, here is a reproducible example (tested both on WinXP and Linux): > x <- ts(cbind(1:5,1:5)) > x Time Series: Start = 1 End = 5 Frequency = 1 Series 1 Series 2 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 > class(x) [1] "mts" "ts" > edit(x)

Dear all, I am puzzled at the behaviour of is.loaded() when a dyn.load() call to a a FORTRAN shared library is included in a file to be sourced. A reproducible example is the following: 1. the attached fortran subroutine try_it.f90 performs a summation of the elements of a REAL*8 vector compile with gfortran try_it.f90 -shared -s -otry_it.dll 2. create a file to be sourced (see the attached