[Rd] warnings with plot=FALSE in hist.default

2006-10-11 Thread Deepayan Sarkar
Hi, the NEWS for R 2.4.0 has: o hist(*, plot = FALSE) now warns about unused arguments. I'm sure this does some good for someone somewhere, but it causes lattice::histogram() calls to produce warnings now in certain cases, which I need to fix. However, ?hist makes no mention of this new st

Re: [Rd] Compiling R 2.4.0 in ubuntu/linux

2006-10-11 Thread James Bullard
Gavin Simpson wrote: > On Wed, 2006-10-11 at 17:58 -0400, T C wrote: >> I'm not sure if this is the place to post this question, but, I am >> having trouble compiling the source code. I do have a suitable C >> compiler and f2c but I get this error when I run ./configure >> >> configure: error: --

Re: [Rd] Compiling R 2.4.0 in ubuntu/linux

2006-10-11 Thread Gavin Simpson
On Wed, 2006-10-11 at 17:58 -0400, T C wrote: > I'm not sure if this is the place to post this question, but, I am > having trouble compiling the source code. I do have a suitable C > compiler and f2c but I get this error when I run ./configure > > configure: error: --with-readline=yes (default) a

Re: [Rd] Possible bug in accessing methods documentation?

2006-10-11 Thread Martin Morgan
Seth's example is really good -- ExpressionSet extends eSet, and featureNames is defined on eSet rather than ExpressionSet. To live up to the documentation, we should end up at the help page with \alias{featureNames,eSet-method}. A simpler example from the same package is ?exprs(sample.ExpressionS

[Rd] Compiling R 2.4.0 in ubuntu/linux

2006-10-11 Thread T C
I'm not sure if this is the place to post this question, but, I am having trouble compiling the source code. I do have a suitable C compiler and f2c but I get this error when I run ./configure configure: error: --with-readline=yes (default) and headers/libs are not available Any ideas? Thanks. _

Re: [Rd] Possible bug in accessing methods documentation? (PR#9291)

2006-10-11 Thread Duncan Murdoch
On 10/11/2006 4:26 PM, [EMAIL PROTECTED] wrote: > On 10/11/2006 2:48 PM, Seth Falcon wrote: >> Hi, >> >> Reading help("Documentation"), I'm led to believe that a help call >> like: >> >> ?myFun(x, sqrt(wt)) >> >> Will search for help on the appropriate method in the case that myFun >> is generi

Re: [Rd] Possible bug in accessing methods documentation? (PR#9291)

2006-10-11 Thread murdoch
On 10/11/2006 2:48 PM, Seth Falcon wrote: > Hi, > > Reading help("Documentation"), I'm led to believe that a help call > like: > > ?myFun(x, sqrt(wt)) > > Will search for help on the appropriate method in the case that myFun > is generic. This isn't working for me. Here is an example using

[Rd] Possible bug in accessing methods documentation?

2006-10-11 Thread Seth Falcon
Hi, Reading help("Documentation"), I'm led to believe that a help call like: ?myFun(x, sqrt(wt)) Will search for help on the appropriate method in the case that myFun is generic. This isn't working for me. Here is an example using the Biobase package: ## If Biobase is not installed source

Re: [Rd] dispatching on group generics with more than one formal

2006-10-11 Thread John Chambers
Yes, a bug. The problem is that all generics start off with only 1 active argument in the signature (for efficiency). As soon as a method is specified with >1 args in the signature, the number of active arguments is supposed to be incremented accordingly. But specifying the method for the _g

Re: [Rd] operator :: and symbols not in the namespace of a package with a namespace

2006-10-11 Thread Seth Falcon
Prof Brian Ripley <[EMAIL PROTECTED]> writes: > The reason was (and is) that if datasets are in the namespace, functions > in the namespace find them ahead of a dataset of the same name in the > user's workspace. That this is desirable seems to be where opinions differ. The Bioconductor proje

Re: [Rd] nls function does not use subset argument (PR#9290)

2006-10-11 Thread Tadashi Kadowaki
I am sorry, it was my program's bug. Yes, subset works! Yes, nls works correctly! I didn't pay enough attention to NAs. NA threw off start value estimation in my program. So, I got different results when I filtered NAs beforehand and filtered by subset. I also confused because subset does not appe

Re: [Rd] nls function does not use subset argument (PR#9290)

2006-10-11 Thread Peter Dalgaard
[EMAIL PROTECTED] writes: > Full_Name: Tadashi Kadowaki > Version: 2.4.0 > OS: Redhat Linux 9 > Submission from: (NULL) (58.12.166.67) > > > Doesn't nls function support subset? It seems not to work. > And, there are no information in the online help. > Has it sunk into oblivion? Whatever gave

Re: [Rd] nls function does not use subset argument (PR#9290)

2006-10-11 Thread Prof Brian Ripley
This is not the place to ask a question: do read the FAQ. ?nls shows that nls does have a 'subset' argument, and it does work. Compare > ?nls > x <- 1:10 > y <- 2*x + 3# perfect fit > yeps <- y + rnorm(length(y), sd = 0.01) # added noise > nls(yeps ~ a + b*x, start = l

[Rd] nls function does not use subset argument (PR#9290)

2006-10-11 Thread tadakado
Full_Name: Tadashi Kadowaki Version: 2.4.0 OS: Redhat Linux 9 Submission from: (NULL) (58.12.166.67) Doesn't nls function support subset? It seems not to work. And, there are no information in the online help. Has it sunk into oblivion? __ R-devel@r-p

Re: [Rd] expression as a parameter of binom.test (PR#9288)

2006-10-11 Thread ripley
On Wed, 11 Oct 2006, Roger Bivand wrote: > On Wed, 11 Oct 2006 [EMAIL PROTECTED] wrote: > >> Full_Name: Petr Savicky >> Version: 2.4.0 >> OS: Fedora Core release 2 >> Submission from: (NULL) (62.24.91.47) >> >> >> the error is >> >>> binom.test(0.56*1,1) >> Error in binom.test(0.56 * 1

Re: [Rd] expression as a parameter of binom.test (PR#9288)

2006-10-11 Thread Roger Bivand
On Wed, 11 Oct 2006 [EMAIL PROTECTED] wrote: > Full_Name: Petr Savicky > Version: 2.4.0 > OS: Fedora Core release 2 > Submission from: (NULL) (62.24.91.47) > > > the error is > > > binom.test(0.56*1,1) > Error in binom.test(0.56 * 1, 1) : > 'x' must be nonnegative and

Re: [Rd] possible bug? (PR#9285)

2006-10-11 Thread Prof Brian Ripley
This is a problem in a (non-CRAN) contributed package, and so a misuse of R-bugs: please do read the R FAQ and posting guide. Binary versions of packages need to be matched to versions of R: almost certainly this needs to be re-installed from the sources (which it seems that author is not distr