similar to: rm error on Windows after R CMD INSTALL

On Solaris when my package is built, I get the following result: creating vignettes ...Segmentation Fault - core dumped OK My question isn't why I get a segfault, but why does build return an OK after such an inauspicious event? Is build only supposed to error out if something more central to the package is off? R CMD check does issue a warning that the vignette is missing, so maybe that

Hi all, Most of the analyses I do are short little once-and-done type things that are easily encapsulated in a .Rnw file. However, I sometimes end up with projects that take an extended amount of time. Usually these projects are not easily encapsulated in an .Rnw file, so I have been using a single .R file with lots of comments. The problem with this approach is keeping track of what you have

I just built R-devel from source on OS X (Tiger), using the subversion sources. Running ./tools/rsync-recommended didn't download rcompgen. I checked http://cran.r-project/src/contrib/2.7.0/Recommended and indeed, this package is not there. If I try to install using install.packages I get > install.packages("rcompgen", type="source") --- Please select a CRAN

Hi, I have a package that contains two vignettes that both use saved objects in the examples directory of the package. With previous versions of R I could have a code chunk in the vignette like this: <<echo=false>>= load("../examples/somedata.Rdata") @ followed by a code chunk like <<eval=false>>= foo <- bar("data") @ that simulated the actual

The function knn.cv in the class package doesn't have error checking to ensure that the length of the classlabel argument is equal to the number of rows in the test set. If the classlabel is short, the result is often a segfault. > library(class) > dat <- matrix(rnorm(1000), nrow=10) > cl <- c(rep(1,5), rep(2,5)) > cl2 <- c(rep(1,5), rep(2,4)) > knn.cv(dat, cl) [1] 2

> R.version.string [1] "R version 2.1.0, 2005-03-17" I don't see anything in either https://svn.r-project.org/R/trunk/NEWS or in the Changes file for R-2.1.0 about changes in package.skeleton() (nor in the help page), but when I run this function, all the .Rd files produced are of the data format even if all I have in my .GlobalEnv are functions. A trivial example is to run the

Hi all, In the CHANGES file for R-2.3.0alpha, there is the following statement: winMenuAdd() now has no limits on the number of menus or items, and names are now limited to 500 (not 50) bytes. However, I can reproducibly get a segfault using this (admittedly silly) example: for( i in 1:5) winMenuAdd(paste("Test", letters[i], sep="")) for(i in 1:5) for(j in 1:24)

Using R-1.8.0 (d/l and compiled on 2003-10-01) on WinXP, I seem to be unable to determine the maximum memory allocated to R. The help still says to use memory.limit(size=NA), but this returns the value NA. In addition, I have set --max-mem-size=2G but I run out of memory somewhere around 500Mb (which is why I am trying to find out how much memory is allocated). I don't have any other programs

I get a segfault when using savePlot("foo","pdf"). FWIW, I don't have a problem using the canonical pdf("foo.pdf") plot(something) dev.off() Best, Jim > R.Version() $platform [1] "i386-pc-mingw32" $arch [1] "i386" $os [1] "mingw32" $system [1] "i386, mingw32" $status [1] "Under development (unstable)"

If one wants to unload compiled code for a package containing a namespace, my understanding is that .onUnload() should be used, with a call to library.dynam.unload(). This is used in e.g., the stats and methods packages, but it appears to me that the compiled code is not being unloaded when the package is detached(). Am I misunderstanding something? Best, Jim > search() [1]

Hi, I am unable to build a package I maintain using a relatively current build of R-2.4.0 alpha, whereas the package builds just fine on R-2.3.1. Both versions of R were built from source. I'm hoping a guRu might be able to give some help. Some snippets from the build process: R-2.3.1 making DLL ... gcc -Ic:/R-2.3.1/src/extra/zlib -DHAVE_ZLIB -Ic:/R-2.3.1/include -Wall -O2 -c

Aren't the headers usually in the devel package (e.g., fftw-devel-2.1.5-0.dag.rh73.i386.rpm)? You might try installing the devel package too. HTH Jim James W. MacDonald Affymetrix and cDNA Microarray Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC Ann Arbor MI 48109 734-647-5623 >>> Rick Bilonick <rab at nauticom.net> 10/07/03 03:39PM

On windows you will probably get better results if you use flush.console() instead of cat() inside long running functions. HTH, Jim James W. MacDonald Affymetrix and cDNA Microarray Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC Ann Arbor MI 48109 734-647-5623 >>> <peter_mcmahan@yahoo.com> 03/02/04 11:36AM >>> Full_Name: Peter McMahan

On windows you will probably get better results if you use flush.console() instead of cat() inside long running functions. HTH, Jim James W. MacDonald Affymetrix and cDNA Microarray Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC Ann Arbor MI 48109 734-647-5623 >>> <peter_mcmahan@yahoo.com> 03/02/04 11:36AM >>> Full_Name: Peter McMahan

Hi all, This is either a feature request or a plea for help (depending on whether or not I am missing something). I am trying to write a function that will load a package of a particular version, but the package installation was most likely not versioned e.g., --with-package-version For instance, say there are two packages, foo_1.2.3 and foo_1.3.4, and they are installed in two different

Note that package.descripton() is deprecated in R-1.9.0. You have to use packageDescription() instead. Jim James W. MacDonald Affymetrix and cDNA Microarray Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC Ann Arbor MI 48109 734-647-5623 >>> Sundar Dorai-Raj <sundar.dorai-raj at PDF.COM> 03/30/04 10:51AM >>> You can access this from

I don't know of a good tutorial, but I find that looking at ?par is usually good for answering most graphing questions. To resize axes, look at xlim and ylim under ?par. As for changing the axes, you can suppress the axes using e.g., for the x-axis xaxt="n" in your plotting function call, and then add your own axis using the axis() function (see ?axis). HTH, Jim James W.

Hi All, I am having a problem with Rcmd build using R-devel on WinXP. If I try to build a package using the --binary flag, I get the following error: Error: cannot change to directory ' 'c:/TEMP/Rbuild.XXXX' ' Where XXXX is some number. I can get Rcmd build to work using R-1.7.1 and R-1.8.0, so I don't think it is a permission problem. I looked at the build file, and the

Hi All, I am having a problem with Rcmd build using R-devel on WinXP. If I try to build a package using the --binary flag, I get the following error: Error: cannot change to directory ' 'c:/TEMP/Rbuild.XXXX' ' Where XXXX is some number. I can get Rcmd build to work using R-1.7.1 and R-1.8.0, so I don't think it is a permission problem. I looked at the build file, and the

Hi all, Bioconductor has several metaData packages that contain quite large data sets. In the past, these data were simply held in the /data directory of the package as .rda files and load()ed as needed. Converting to using lazy data loading may have memory and performance advantages, but for the larger metaData packages the installation is painfully slow (it has taken > 30 min to install a