similar to: surprising behavior of match.arg() (PR#872)

I'm having trouble figuring out how to create a function using "body<-" (). The help file for body() says that the argument should be a list of R expressions. However if I try that I get an error: > tmpfun <- function(a, b=2){} > body(tmpfun) <- list(expression(z <- a + b),expression(z^2)) Error in as.function.default(c(formals(f), value), envir) :

When I run Rcmd check on a package on my Windows 2000 machine, I get a series of error messages like the following: * checking generic/method consistency ...c:\DOCUME~1\R5018~1.WOO\LOCALS~1\Temp/R utils138414013: cannot open c:DOCUME~1R5018~1.WOOLOCALS~1Temp/Rin138408157: no s uch file It looks as if a Windows style path to the temp directory is not being interpreted correctly, with backslashes

Greetings, I have a meta-analysis problem in which I have fixed effects regression coefficients (and estimated standard errors) from identical models fit to different data sets. I would like to use these results to create pooled estimated regression coefficients and estimated standard errors for these pooled coefficients. In particular, I would like to estimate the model \beta_{i} = \mu +

When I try to open a server socket on the system setup listed below, I get the following error: > a <- make.socket(port=8091,server=TRUE) Error in make.socket(port = 8091, server = TRUE) : sockets are not available on this system I just wanted to make sure that sockets were generally available for this platform (or, perhaps, I need to upgrade to 1.2.2 on this system), before I got

I have a package that solves systems of ordinary differential equations coded as an R function (odesolve, on CRAN). The function is passed to R code, and c and Fortran code called by it uses lang4() and eval() to evaluate the R function inside a compiled c function to use in a compiled ODE solver. This works quite well, but can be slow. I'd like to be able to supply the name of a compiled

I found that predict.gnls failed with a wierd error message about a non-numeric argument to a binary vector in one of three nearly identical uses. Error in Inh/Ki : non-numeric argument to binary operator (Inh and Ki are arguments to the function used in the formula for the object whose predictions were requested). It turns out that the problem is in getCovariateFormula(). The final line in

Does the following indicate that I have a memory leak? > gc(TRUE) Garbage collection 22891 = 21012+1557+322 (level 2) ... 483257 cons cells free (59%) 11.0 Mbytes of heap free (82%) used (Mb) gc trigger (Mb) Ncells 334906 9.0 818163 21.9 Vcells 309342 2.4 1746173 13.4 > memory.size()/1024/1024 ## in MB [1] 643.8978 > sum(sapply(ls(all.names=TRUE),object.size)) [1] 1776

I think this is a bug; at least this behavior is not documented in plot or plot.default. plot.default resets xaxp, and leaves xaxp reset when it exits: par(xaxp=c(0,1,4)) print(par("xaxp")) plot(c(0,1),c(0.2,0.3)) print(par("xaxp")) R. Woodrow Setzer, Jr. Phone: (919) 541-0128 Experimental Toxicology Division

Hi, I am trying to solve a model that consists of rather stiff ODEs in R. I use the package ODEsolve (lsoda) to solve these ODEs. To speed up the integration, the jacobian is also specified. Basically, the model is a one-dimensional advection-diffusion problem, and thus the jacobian is a tridiagonal matrix. The size of this jacobian is 100*100. In the original package

Probably I've just misread the documentation, but I don't understand the behavior of .Alias. Consider this (on R-1.1.1, both Windows and SGI): > tmp <- matrix(nrow=3,ncol=2) > new <- .Alias(tmp) > new[1,1] <- 1 > tmp [,1] [,2] [1,] NA NA [2,] NA NA [3,] NA NA > new [,1] [,2] [1,] 1 NA [2,] NA NA [3,] NA NA I expected tmp[1,1] to

The binary package (version of 6/17) of rw1051 for Windows is missing html documentation for dyn.load() The file is present in $R_HOME/library/base/html, but has zero bytes. dyn.load help IS accessible through the windows help system. platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 1 minor 5.1 year 2002 month 06 day 17 language R

I would like to be able, inside a function, to create a new function, and use it as part of a formula as an argument to, say, gnls or nlme. for example: MyTop <- function(data=dta) { Cexp <- function(dose,A,B,m){...} Model <- as.formula(paste("y","~ Cexp(",paste(formals(Cexp),collapse =", "),")")) MyCall <-

A couple of minor points about the odesolve package (which I am otherwise enjoying very much): 1. "scalar" is misspelled as "scaler" in the definitions of the rtol and atol parameters 2. it is possible to crash R by doing something dumb, e.g failing to read the documentation carefully enough and (a) returning only a vector of derivatives and not a list of (derivatives,

I think qqline does not do exactly what it is advertised to do ("`qqline' adds a line to a normal quantile-quantile plot which passes through the first and third quartiles."). Consider the graph: tmp <- qnorm(ppoints(10)) qqnorm(tmp) qqline(tmp) The line (which I expected go through all the points), has a slightly shallower slope than does the points plotted by qqnorm. I think

This is in Windows 98. The problem exists in both rw1021 and rw1023, using ActiveState Perl builds 620 and 626: C:\>Rcmd REMOVE --library=C:/R/Rlibs RBMDS Unknown option: library Usage: Rcmd REMOVE [options] pkgs Remove the add-on packages specified by pkgs from the default library tree (/library) or the tree specified via `--library'. Options: -l, --library=LIB remove packages

In the following code routine 'initaquaphy' is defined in Fortran, and dynamically loaded into R.: test.f: subroutine initaquaphy(odeparms) external odeparms double precision pars(19) common /myparms/pars call odeparms(19, pars) return end $ R CMD SHLIB Aquaphy.f gfortran -fpic -g -O2 -c test.f -o test.o gcc -std=gnu99 -shared

I am beginning a much-delayed update of odesolve to include several ordinary differential equation solvers from the Livermore package ODEPACK. These are much-used and reliable Fortran codes, and I plan (as I did for lsoda in the current odesolve package) to make as few changes as possible to the Fortran 77 code. However, recently someone wanted to make nested calls to lsoda, which will not work,

I am having trouble getting smooth-appearing curves in figures produced as windows metafiles using R (R-1.1.1 on Windows 98). When I import them into a word processor (either MS Word 97, or WordPerfect 9.0), the figures appear only slightly bumpy on screen, but when printed, there is a clear jaggedness reminiscent of aliasing. Is there a fix for this (if the answer is "upgrade to 1.2",

Hello there, Suppose you want to solve the following system of ODE's (a simple Lotka-Volterra predator prey model) dP/dt = beta*P*V - mu*P dV/dt = r*V - beta*P*V where P and V are the numbers of predators and prey. Now, this is easy to do, but suppose you have a system of equations like this, dP1/dt = beta1*P1*V1 - mu1*P1 dP2/dt = beta2*P2*V2 - mu2*P2 dV1/dt = r1*V1 - beta1*P1*V1

I am experimenting with exporting pointers to some of the functions in deSolve so that other packages may import them, using the 'R_RegisterCCallable' mechanism. I have added a header file and some other C code in inst/include of the deSolve source package that need to be accessible to other packages. I have a site-library set up in Rprofile.site where all installed packages go, and as