[Rd] input file and console command size limit (PR#7030)

2004-06-29 Thread jerome . mutterer
Full_Name: j m Version: 1.9.0 OS: Mac OsX 10.3.4 Submission from: (NULL) (130.79.19.4) I noticed a 1024 characters size limit when entering R commands in the R console or when calling R from the command line using something like >R $R_in_opts $r_inputfile $R_out_opts $r_outputfile ___

Re: [Rd] Segmentation fault in .Call() (PR#4761)

2003-10-27 Thread Jerome Asselin
I have reviewed the BUGS section of the FAQ. I did not realise that .Call() was an exception in this case. Please accept my sincere apologies. Jerome Asselin On October 24, 2003 11:44 pm, Prof Brian Ripley wrote: > Your expectations are wrong: please re-read the section on BUGS in the &g

[Rd] Segmentation fault in .Call() (PR#4761)

2003-10-24 Thread jerome
Full_Name: Jerome Asselin Version: 1.8.0 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.177.13) I would not expect a segmentation fault; perhaps an error message. > .Call("log") Segmentation fault This is always reproducable for me. Sincerely, J

[Rd] Re: fisher.test() gives wrong confidence interval (PR#4019)

2003-08-30 Thread jerome
Forgot to mention... I'm using R 1.7.1 on Red Hat Linux 7.2. __ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel

[Rd] fisher.test() gives wrong confidence interval (PR#4019)

2003-08-30 Thread jerome
ose(9,n11)*choose(15-9,13-n11)*theta^n11/ sum(choose(9,n11)*choose(15-9,13-n11)*theta^n11) #[1] 0.5608724 0.3891316 0.0499960 Sincerely, Jerome Asselin -- Jerome Asselin (Jérôme), Statistical Analyst British Columbia Centre for Excellence in HIV/AIDS St. Paul's Hospital, 608 - 1081 Burrar

[Rd] segmentation fault: formula() with long variable names(PR#3680)

2003-08-14 Thread jerome
R version: 1.7.1 OS: Red Hat Linux 7.2 In this example, I would expect an error for the overly long variable name. This is always reproducable for me. > formula(paste("y~",paste(rep("x",5),collapse=""))) Segmentation fault Sincerely, Jerome Ass

[Rd] NA's in eigen(), La.eigen() (PR#3723)

2003-08-14 Thread jerome
error message whenever NA's are present in the input matrix. Sincerely, Jerome Asselin ## La.eigen(matrix(c(1,0,0,1),2,2)) #Works La.eigen(matrix(c(1,NA,0,1),2,2)) #Returns something La.eigen(matrix(c(1,0,0,NA),2,2))

[Rd] covmat argument in princomp() (PR#3682)

2003-08-14 Thread jerome
xample: pc2$center is all NA's. Jerome Asselin x <- rnorm(6) y <- rnorm(6) X <- cbind(x,y) pc1 <- princomp(X) pc1$scores %*% t(pc1$loadings)-X pc1$center pc2 <- princomp(X,covmat=cov(X)*5/6) pc2$scores %*% t(pc2$loadings)-X pc2$center # All NA's (should be the same as pc1$ce

[Rd] model.frame() call from inside a function (PR#3671)

2003-08-14 Thread jerome
data, environment()) in model.frame.default() fixes this problem. I don't know if this correction would create more problems in other cases. Perhaps there is a better fix. Sincerely, Jerome Asselin -- Jerome Asselin (Jérôme), Statistical Analyst British Columbia Centre for Excellence in HIV

Re: [Rd] segmentation fault: formula() with long variable names(PR#3680)

2003-08-09 Thread Jerome Asselin
Indeed, I don't want to do that. (I found the bug by mistake.) Maybe I'm wrong, but I thought that all segmentation faults should be reported. This one is certainly not an urgent issue. Cheers, Jerome On August 7, 2003 02:30 pm, Peter Dalgaard BSA wrote: > [EMAIL PROTECTED]

Re: [Rd] model.frame() call from inside a function (PR#3671)

2003-08-09 Thread Jerome Asselin
e documentation. Personally, I think this is safe, because the expression eval(subset, data, env) is still evaluated in the environment of `formula', despite the fact that this environment has changed. Sincerely, Jerome Asselin foo <- function(formula,data,subset=NULL) { cat("

[Rd] "na.action" parameter in princomp() (PR#3481)

2003-07-14 Thread jerome
Full_Name: Jerome Asselin Version: 1.7.1 OS: Red Hat Linux 7.2 Submission from: (NULL) (24.77.125.119) Setting the parameter na.action=na.omit should remove incomplete records in princomp. However this does not seem to work as expected. See example below. Sincerely, Jerome Asselin data

Re: [Rd] degrees of freedom in nlme() (PR#2384)

2003-07-03 Thread jerome
12 12 12 12 12 12 12 12 12 12 I agree that in principle linear mixed-effects models should be fit with lme(), not nlme(). However, nlme() may return the wrong number of degrees of freedom without warning and because of that I believe this issue should be considered seriously. Sincerely, Jerome A

Re: [Rd] "trace" argument in legend() (PR#2578)

2003-05-29 Thread jerome
Another easy fix for legend() with trace=TRUE would be to replace "...)" by ", ...)" in this code: [...] if (trace) catn(" rect2(", left, ",", top, ", w=", w, ", h="

[Rd] [R] (PR#2720)

2003-04-03 Thread jerome
d I have tried to find the source of the problem, but no success. You can check what I found so far at: http://r-bugs.biostat.ku.dk/cgi-bin/R/Add-ons?id=2384 Can anyone help find the source of this problem? Sincerely, Jerome Asselin R 1.6.2 on Red Hat Linux 7.2 Package: nlme 3.1-38

[Rd] lme() and nlme() give inconsistent numbers of degrees of freedom(PR#2384)

2003-04-01 Thread jerome
d I have tried to find the source of the problem, but no success. You can check what I found so far at: http://r-bugs.biostat.ku.dk/cgi-bin/R/Add-ons?id=2384 Can anyone help find the source of this problem? Sincerely, Jerome Asselin R 1.6.2 on Red Hat Linux 7.2 Package: nlme 3.1-38

[Rd] plot() with type="s" and lty=2 (PR#2630)

2003-03-12 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.2 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.173.179) In the following example, the line type lty=2 does not show properly across the entire line. x <- c(seq(0,.5,.001),seq(.6,1,.1)) y <- rep(1,length(x)) plot(x,y,type="s",l

Re: [Rd] "trace" argument in legend() (PR#2578)

2003-02-27 Thread jerome
Oops. I forgot this one. We should also replace "...)" by ", ...)" in this part of the code. [...] if (trace) catn(" points2(", x1, ",", y1, ", pch=", pch[ok], "...)") [...] Jerome On Tuesday 25

[Rd] "trace" argument in legend() (PR#2578)

2003-02-24 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.2 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.173.179) Should be an easy fix... Consider the examble below: plot(0,0) legend(0,0,c("Hello!","Hi!"),pch=1:2,lty=1:2,trace=T) It gives the following trace: > plot(0,0) >

[Rd] table() with option "exclude=NULL" (PR#2491)

2003-01-24 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.2 OS: redhat linux 7.2 Submission from: (NULL) (142.103.173.179) Bug or feature? Hard to say... But it sure would be nice if table() would label the frequency of NA's as it does for NaN's. Regards, Jerome > table(c(2,NA,1,1,1),exclude=NUL

[Rd] package mvtnorm: sigma parameter in pmvnorm() (PR#2478)

2003-01-20 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.2 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.173.179) pmvnorm() may fail for a univariate distribution when its parameter "sigma" is defined as a matrix. It will fail if sigma < 1. library(mvtnorm) #THIS WORKS > pmvnorm(lower=-

[Rd] chron package: delimiter for dates (PR#2458)

2003-01-15 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.1 OS: redhat linux 7.2 Submission from: (NULL) (142.103.173.179) The option <> fails. Package: chron Version: 2.2-22 > library(chron) > chron("01 May 2002",format="day month year") [1] 01 May 2002 > chron("01-May

Re: [Rd] degrees of freedom in nlme() (PR#2384)

2003-01-06 Thread jerome
I believe that a round-off error is causing nlme() to provide a wrong number of degrees of freedom. In the example below, getFixDF() returns 2 degrees of freedom, but it should be 12 degrees of freedom according to lme(). R 1.6.1 on RedHat Linux 7.2 Package: nlme Version: 3.1-36 Date: 2002-12-28

[Rd] degrees of freedom in nlme() (PR#2384)

2002-12-19 Thread jerome
Full_Name: Jerome Asselin Version: 1.6.1 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.173.179) There is something very queer happening with the degrees of freedom in nlme(). In the example below, I am fitting the same model with lme() and nlme(). I am using the nlme package version 3.1