similar to: package.skeleton

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

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 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

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

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 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 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)"

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

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)

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

Hi the devel list. I am adapting the package.skeleton to S4 classes and methods I would have been very proud to post a new working function on this list. Unfortunately, I do not manage to solve all the problems. Mainly - sys.source does not compile a file with setClass - dumpMethod does not exists yet In the following code, thise two problems are notified by a line ################# Still

I've tried looking at ?colors and ?palette and if I'm understanding it correctly, I'm supposed to type in (for example) palette(rainbow(13)) before I type in my plot (of 13 lines) if I want 13 different colors. But this does not work. Other things that i have tried besides rainbow give me errors. Am I just doing something completely wrong? Anna

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

I get the following error when building R from the subversion server as well as the latest tarball. I am on Windows XP, and I recently updated my MinGW installation. It's quite possible I am doing something wrong, but I am not sure what that might be. making console.d from console.c making dataentry.d from dataentry.c making dynload.d from dynload.c making edit.d from edit.c making editor.d

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

As far as I know, the following should work. Can anybody tell me if/where I am going wrong? > packageDescription("KEGG", field="Version") [1] "1.6.4" > require(KEGG, version="1.6.4") Loading required package: KEGG [1] FALSE Warning message: There is no package called 'KEGG', version 1.6.4 in: library(package, character.only = TRUE, logical

Hi everyone, My purpose is to read a .CEL file into R. The .CEL file was created from a .CAB by using DTT software found on Affymetrix website I read the .CEL file in R using ReadAffy as follows: > d2=ReadAffy(widget=T) and I complete the fields as required. It does not complain. For example I could find the description: > description(d2) Experimenter name: BB Laboratory: FFL Contact

I am running R 2.0.0, GOstats 1.1.1 and GO 1.7.0, and when I use the function GOHyperG, I have the following error: w1<-as.list(hgu95av2LOCUSID) w2<-unique(unlist(w1)) set.seed(123) myLL<-sample(w2,100) xx <- GOHyperG(myLL) Error in mget(x, env = GOTERM, ifnotfound = NA) : recursive default argument reference In fact first I tried this function with my locusId ' list (with

I am trying to work with 75 affymetrix U133plus2 chips and am running into memory allocation errors when trying to merge or convert probe level data to expression values. I keep getting - Error: cannot allocate vector of size 561011 Kb and that is simply with a data subset. Is there a way around this limitation? -- Rodney A. Staggs Cancer Center Informatics Shared Resource 425 Delaware St S.E.