[EMAIL PROTECTED] wrote:
> Hi,
>
> I have been compiling R from source code with regularity (both R-patched
> and R-devel) for several months now. About two/three weeks ago I noticed a
> compilation error in R-devel (see below). I thought that the error will go
> away in "due course" so I did no
Hi,
thanks for the report - but it should have gone to the Bioconductor
list, and the package maintainer, thanks.
New versions of multtest and a few other packages will percolate up in
the next few days to resolve the problem.
Best wishes,
Robert
[EMAIL PROTECTED] wrote:
> Full_Name
Hi,
thanks for the report - but it should have gone to the Bioconductor
list, and the package maintainer, thanks.
New versions of multtest and a few other packages will percolate up in
the next few days to resolve the problem.
Best wishes,
Robert
[EMAIL PROTECTED] wrote:
> Full_Name
Hi,
I have been compiling R from source code with regularity (both R-patched
and R-devel) for several months now. About two/three weeks ago I noticed a
compilation error in R-devel (see below). I thought that the error will go
away in "due course" so I did not investigate it further. Then I lef
> lgautier writes:
> Full_Name: Laurent
> Version: R-2.0.0-beta-from-a-week-ago
> OS: linux
> Submission from: (NULL) (202.156.6.77)
> When running 'R CMD check' for a package that contains the symbol '%'
> in the signature of a function (say the default parameter for a string
> argument is
Full_Name: Ken Kompass
Version: 2.2.0
OS: winXP pro (2002 version, SP2)
Submission from: (NULL) (128.252.149.244)
Using R2.2.0 I get this error msg when loading certain bioconductor libraries
(depending on whether the library contains file named "all.rda" in R folder of
library) :
> library(mult
Hi,
Following the Writing R Extensions manual, I created a method for the
cor function. As cor is not a generic, I followed the advice of section
6.1 of the same manual and did the following:
cor <- function(x, ...) UseMethod("cor")
cor.default <- stats::cor
cor.symcoca <- function{ some code }
On Mon, 10 Oct 2005, Hjellvik Vidar wrote:
> Hello,
>
> I have used the arima.sim function to generate a lot of time series, but to
> day I got som results that I didn't quite understand. Generating two time
> series z0 and z1 as
>
> eps <- rnorm(n, sd=0.03)
> z0 <- arima.sim(list(ar=c(0.9)), n=
Hello,
I have used the arima.sim function to generate a lot of time series, but to day
I got som results that I didn't quite understand. Generating two time series z0
and z1 as
eps <- rnorm(n, sd=0.03)
z0 <- arima.sim(list(ar=c(0.9)), n=n, innov=eps)
and
z1 <- arima.sim(list(ar=c(0.9)), n=n,
> What I would like to have:
> Of course there would be many different ways to accomplish this. Here are
> some solutions I can think of:
I just had an additional idea:
4) Export inError, and inWarning from errors.c:
I'm not entirely sure this would really work as expected, but if it did, it
woul
Hi all,
I'm working on a GUI frontend for R, and I'm looking for a good way to catch
all warning- and error-output. The reason for this is mostly, that I would
like to know, which sections of the output are "normal" output, warnings, and
errors. This would allow for some nice features, such as
Full_Name: Laurent
Version: R-2.0.0-beta-from-a-week-ago
OS: linux
Submission from: (NULL) (202.156.6.77)
When running 'R CMD check' for a package that contains the symbol '%'
in the signature of a function (say the default parameter for a string argument
is like "10% - 20%"), the 'codoc' part of
12 matches
Mail list logo
