similar to: suppressing 'download.file' progress window

When I build R-devel (or the alpha snapshots) on a system without makeinfo >= 4.7, I get a warning about not being able to build HTML/Info help pages after running 'configure' (but 'make' runs smoothly and there are no errors). However, when I run 'make install' I get an error, something like make[2]: Entering directory

Hi (Roger), I saw the announcement of filehash v2.0 and the sentence "This development has lead to better file locking for concurrent access and faster reading and writing of data in general" caught my attention. What kind of file locking do you refer to here? I am looking for a mechanism that can be used to lock files for reading and/or writing, and I'd love to have a cross

In R 1.9.0 on Solaris/Sparc when I run, for example, install.packages("gregmisc", "~/R-local/lib"), instead of installing the `gregmisc' package in the directory /users/student/rpeng/R-local/lib the package gets installed in /users/student/rpeng/\~/R-local/lib, so the directory \~ is created in my home directory. This doesn't happen to me on Linux or Windows so I

The 'cacher' package contains a set of routines for caching statistical analyses. The idea is that an analysis stored in a file (say, 'foo.R') is run and the results of the evaluated expressions are cached in a database. These cached results can subsequently be packaged up and distributed over the interweb. I've just uploaded to CRAN version 0.1-2 of the 'cacher'

The 'cacher' package contains a set of routines for caching statistical analyses. The idea is that an analysis stored in a file (say, 'foo.R') is run and the results of the evaluated expressions are cached in a database. These cached results can subsequently be packaged up and distributed over the interweb. I've just uploaded to CRAN version 0.1-2 of the 'cacher'

I've noticed recently that 'update.packages' and 'install.packages' seem to not do tilde expansion anymore, i.e. when I run update.packages("~/R-local/lib") on R-alpha (r41043) I get the message /home/rpeng/install/R-alpha/lib64/R/bin/INSTALL: line 304: cd: ~/R-local/lib: No such file or directory and the package is subsequently installed in the current working

Are the functions 'R_Unserialize' and 'R_InitFileInPStream' allowed to be used in R packages? I guess I'm just not clear on the implications of this comment in 'Rinternals.h': /* The connection interface is not yet available to packages. To allow limited use of connection pointers this defines the opaque pointer type. */ I have a function in the

Since compiling R 2.5.0 from source on my Mac (PowerBook) I've noticed some strange behavior when plotting. I'm not sure if it's a problem with my setup/compilation because I feel like a problem as basic as this one would have been reported already. I'm running R with X11 and R was built with gcc 4.0.1. Basically, I run > plot(0, 0) > dev.off() X11 4 Warning message:

I have just uploaded a package to CRAN called `gpclib' for clipping large and complex polygons. This package provides an R interface to Alan Murta's very fast General Polygon Clipper library (written in C), which has an optimized version of the Vatti algorithm. Not all features of Murta's library are implemented -- right now you can do intersections, differences, and unions. There

I have just uploaded a package to CRAN called `gpclib' for clipping large and complex polygons. This package provides an R interface to Alan Murta's very fast General Polygon Clipper library (written in C), which has an optimized version of the Vatti algorithm. Not all features of Murta's library are implemented -- right now you can do intersections, differences, and unions. There

I've noticed something recently in R-beta that has changed since R 2.4.1 and I'm not sure if it's a readline problem or an R problem. I am on a Linux FC5 system and in R 2.4.1 I could do load("my-directory/ and then hit TAB and it would list all of the files in 'my-directory', after which I could start typing the beginning of the file, hit TAB again, and it would

I've noticed a change in the way grep() behaves between the 1.9.0 release and a recent R-patched. On 1.9.0 I get the following output: > x <- dget(file = url("http://www.biostat.jhsph.edu/~rpeng/names.R")) > length(grep("^l\\w+tmean", x, perl = TRUE, value = TRUE)) [1] 84 And on R-patched (2004-06-11) I get > x <- dget(file =

--KsGdsel6WgEHnImy Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi, people. Wandering in R archives, and seeing the message attached below, I noticed that: mapply(rep,times=1:4, MoreArgs=42) still segfaults on R 2.2.0, and thought I should be a good citizen and report it, even if I do not have an actual problem

I've noticed what I think is curious behavior in using 'sub(fixed = TRUE)' and was wondering if my expectation is incorrect. Here is one example: v <- paste(0:10, "asdf", sep = ".") sub(".asdf", "", v, fixed = TRUE) The results I get are > sub(".asdf", "", v, fixed = TRUE) [1] "0"

As far as I can tell, 'isOpen' cannot return FALSE in the case when 'rw = ""'. If the connection has already been closed by 'close' or some other function, then isOpen will produce an error. The problem is that when isOpen calls 'getConnection', the connection cannot be found and 'getConnection' produces an error. The check to see if it is

On Fri, 12 Mar 2004 11:44:14 -0500, "Roger D. Peng" <rpeng@jhsph.edu> wrote : >Funny, it works for me on R-patched > > > f <- function(a) { return(log(a)) } > > f("A") >Error in log(x) : Non-numeric argument to mathematical function > > traceback() >2: log(a) >1: f("A") > > try(f("A")) >Error in log(x) :

Are there any general guidelines for writing functions that appear in model formulas for functions like lm()/glm()? The ones I can think of are ns()/bs() in `splines' and s() in `mgcv'. It seems that ns()/bs() basically create matrix with a number of attributes and a class, while s() returns a list of parameters. It seems that gam() in `mgcv' has its own way of dealing with

I'm trying to build R-devel with AMD's ACML. I downloaded version 3.0.0 64bit for gfortran (acml-3-0-0-gfortran-64bit.tgz) and copied the libraries to /usr/local/lib. When I configure R to build against the ACML library, how do I know if the library has been detected and will be used? I run 'configure' with the '--with-blas=-lacml' flag and am using gcc 4.0.2 (with

The following paragraph from ?pdf struck me as a bit odd: 'pdf' writes uncompressed PDF. It is primarily intended for producing PDF graphics for inclusion in other documents, and PDF-includers such as 'pdftex' are usually able to handle compression. Should that be "...and PDF-includers such as 'pdftex' are usually _un_able to handle

I'm interested in playing around with memory profiling in R-devel (as described at http://developer.r-project.org/memory-profiling.html) and was trying to figure out how to compile R-devel so that I can use the 'tracemem()' function. But I can't figure out how/where to set R_MEMORY_PROFILING. Is it on the configure command line? Thanks for any help, -roger -- Roger D. Peng