Re: [Rd] Inconsistencies in wilcox.test

So I tried adding Infinity support for all cases. And it is (as could be expected) more complicated than I thought. It is easy to add Inf support for the test. The problems start with conf.int=TRUE. Currently confidence intervals are computed via `uniroot()` and, in the case of infinities, we

Re: [Rd] long vector support

Thank you both. I really appreciate your work developing R, and it is exciting that long vector support may be coming to writeBin(). Next time, I will come prepared with svn revision numbers to help track things down. On Sat, Dec 7, 2019 at 6:17 AM Martin Maechler wrote: > > Will L > >

Re: [Rd] Inconsistent behavior for the C AP's R_ParseVector() ?

On 12/9/19 2:54 PM, Laurent Gautier wrote: > > > Le lun. 9 déc. 2019 à 05:43, Tomas Kalibera > a écrit : > > On 12/7/19 10:32 PM, Laurent Gautier wrote: >> Thanks for the quick response Tomas. >> >> The same error is indeed happening when trying to have

Re: [Rd] Inconsistent behavior for the C AP's R_ParseVector() ?

Le lun. 9 déc. 2019 à 05:43, Tomas Kalibera a écrit : > On 12/7/19 10:32 PM, Laurent Gautier wrote: > > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is this > happen

[Rd] default col.names from data.frame not the same as as.data.frame

Hello, All:   Consider: > data.frame(matrix(1:2, 1))   X1 X2 1  1  2 > as.data.frame(matrix(1:2, 1))   V1 V2 1  1  2   I ask, because I got different default names running the same numbers through BMA:::bic.glm.matrix and BMA:::bic.glm.data.frame, so I thought I'd ask this group wh

Re: [Rd] What should dnorm(0, 0, -Inf) return?

I have committed a fix for r-devel (dnorm only). -pd > On 9 Dec 2019, at 08:49 , Martin Maechler wrote: > >> peter dalgaard >>on Sun, 8 Dec 2019 12:11:50 +0100 writes: > >> Yes, that looks like a bug and an easily fixable one too. > > agreed. > >> However, I spy another issue: W

Re: [Rd] Inconsistent behavior for the C AP's R_ParseVector() ?

On 12/7/19 10:32 PM, Laurent Gautier wrote: > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is > this happening during parsing" (that is why are variables assigned to

Re: [Rd] Inconsistencies in wilcox.test

I'd like to ask the developers to include some exact computation for ties into wilcox.test(). Just try wilcox.test(c(1,1,5),c(10,11)) wilcox.test(c(1,2,5),c(10,11)) The p-values differ significantly. But if I try library(exactRankTests) wilcox.exact(c(1,1,5),c(10,11)) wilcox.exact(c(1,2,5)