similar to: rebuilding vignettes in 2.13-0-alpha fails if name of source dir is not package name

Hope these help for alternatives to lm()? I show the use of a 2nd order polynomial as an example to generalize a bit. Sometimes from the subject line two separate responses can appear as reposts when in fact they are not... (though there are identical reposts too). I should probably figure a way around that. --- Stephen Tucker <brown_emu at yahoo.com> wrote: > ## Data input > input

(Warning: There is some potential that this message is redundant.) I think that i have spotted an issue with R CMD check that does not trace back to a rare case, so it must have been reported already or i am doing something stupid. However, to be sure and because I did not find any comments on this while searching the R mailing lists, here is what i did: R CMD check . from within a package

Dear list, This is related to the change discussed in the thread "no visible binding for global variables for data sets in a package". I went to look at the Check results for one of my packages (analogue) on CRAN: http://cran.r-project.org/web/checks/check_results_analogue.html Under the r-devel build machines I'm seeing a lot of things like this: Stratiplot.default :

It appears that file.copy() does not protect against the case when one copies one directory to a subdirectory of itself resulting in it trying to create and endless recursive copy of itself. REPRODUCIBLE EXAMPLE: src <- "foo" dir.create(src); file.copy(src, src, recursive=FALSE) # ok file.copy(src, src, recursive=TRUE) # PROBLEM

I am compiling the latest R-patched (Revision: 65533) Ubuntu Lucid (10.04). Building succeeds but make check stops with an error. The output in the terminal from make check: Testing examples for package ?base? Testing examples for package ?tools? Error: testing 'tools' failed Execution halted make[3]: *** [test-Examples-Base] Error 1 make[2]: *** [test-Examples] Error 2 make[1]: ***

I'm having a problem rebuilding a package, new to me in R 2.15.0 (Linux) It hits all that contain the line \usepackage[pdftex]{graphics} and leads to the following when running R CMD check on the directory. (I do this often; a final run on the tar.gz file will happen before submission.) Since I float and resize my figures, removing the line is fatal in other ways.

Hi, This is (presumably?) a bug in R 1.7.0 under Windows. I have not tested it on other systems. Attachment of packages is case sensitive but not library(), resulting in multiple loadings of the same package if the library name is spelled differently. The following example loads the `tools' package, once as `tools' and once as `Tools'. This behavior is the same with all packages and

I've rolled up R-1.8.1.tgz a short while ago. This is a patch version mostly fixing a number of issues in 1.8.0, some of which were quite serious. As usual, a few new features have crept in as well. (See below for details.) You can get it from http://cran.us.r-project.org/src/base/R-1.8.1.tgz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will

I've rolled up R-1.8.1.tgz a short while ago. This is a patch version mostly fixing a number of issues in 1.8.0, some of which were quite serious. As usual, a few new features have crept in as well. (See below for details.) You can get it from http://cran.us.r-project.org/src/base/R-1.8.1.tgz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will

Hi folks, I've looked through the list archives and online resources, but I haven't really found an answer to this -- it's pretty basic, but I'm (very much) not a statistician, and I just want to check that my solution is statistically sound. Basically, I have a data file containing two columns of data, call it data.tsv: year count 1999 3 2000 5 2001 9 2002 30 2003 62 2004 154

I haven't figured it out entirely, but it looks like there are a couple of small glitches with knitr-based vignettes and SweaveParseOptions. I posted the tarball of a package with a knitr vignette with (as far as I can tell) everything properly coded in the DESCRIPTION file (VignetteBuilder: knitr, Suggests: knitr) and the vignette itself (%\VignetteEngine{knitr::knitr}). When Windows