similar to: Bug in codetools ?

I've put together a package codetools with some tools for examining R source code. It is available at http://www.stat.uiowa.edu/~luke/R/codetools/codetools.tar.gz It requires a reasonably current version of R-devel. The main user functions are: checkUsage, checkUsageEnv, checkUsagePackage: Examine closure, closures in an environment, closures in a package, and report

Dear R Users, Using codetools I obtained the text representation of the parse tree for this snippet z=quote({x[1]<-2}) showTree(z) > ("{" (<- ([ x 1) 2)) (A) If I understand correctly, x[1]<-2 ought to be "[<-"(x,1,2), so shouldn't i see ("{" ( [<- x 1 2 ) ) If indeed the parse tree in (A) is correct, the operation ([ x 1) returns the

Hi Mr Tierney, I have noticed an error message from R 1.12.x's CMD check for a while (apparently prof Ripley completely rewrote CMD check in R 1.12+) e.g.: http://bioconductor.org/checkResults/2.7/bioc-LATEST/snpMatrix/lamb2-checksrc.html ---------------- * checking R code for possible problems ... NOTE Warning: non-unique value when setting 'row.names': ?new? Error in

Sorry for reposting, i keep forgetting this should be plain text. Will not make this mistake again Hello, The following code moo <- function(a=1){ x=1; x=x+y} funs <- new.env() enter <- function(type, v, e, w){ assign(v, TRUE, funs) } library(codetools) collectUsage(moo, enterGlobal = enter) adds + to the environment funs i.e. funs: "=" "{" "+"

After upgrading to R 2.5.1 on Debian, R CMD check gives * checking Rd cross-references ... WARNING Error in .find.package(package, lib.loc) : there is no package called 'codetools' Execution halted * checking for missing documentation entries ... WARNING etc The NEWS file says (for 2.5.0; I was on 2.4 before the recent upgrade) o New recommended package 'codetools' by Luke

Hi, Currently the `gaussian' family's initialization code signals an error if any response data are zero or negative and a log link is used. Given that zero or negative response data are perfectly legitimate under the GLM fitted using `gaussian("log")', this seems a bit unsatisfactory. Might it be worth changing it? The current offending code from `gaussian' is:

Dear list members, I frequently program small scripts and wrap them into functions to be able to check them with checkUsage. In case these functions (loaded via source or copy pasted to the R console) use functions from other packages, I get this error: no visible global function definition for ?xxxxxxx? For example: test = function() { require(plotrix) color.legend() }

G'day all, I had a look at the GLM code of R (1.4.1) and I believe that there are problems with the function "glm.fit" that may bite in rare circumstances. Note, I have no data set with which I ran into trouble. This report is solely based on having a look at the code. Below I append a listing of the glm.fit function as produced by my system. I have added line numbers so that I

Hi the list Is there any tutorial to learn codetools ? It seems to be a very interesting pacakge, but the help gives not that much detail, and there is not that much examples provided... Christophe

In a package, I define a method for not-yet-generic function 'qr.X' like so: > setOldClass("qr") > setMethod("qr.X", signature(qr = "qr"), function(qr, complete, ncol) NULL) The formals of the newly generic 'qr.X' are inherited from the non-generic function in the base namespace. Notably, the inherited default value of formal

I encountered a segfault running glm() and wonder if it could have something to do with the way memory is handled in a dual core system (which I just set up). I'm running R-base-2.4.0-1, installed from the SuSE 10.1 x86_64 rpm (obtained from CRAN). (My processor is an AMD Athlon 64 x2 4800+). The error and traceback are *** caught segfault *** address 0x8001326f2b, cause 'memory not

Dear List, I'm trying to create a formula method, allowing for a "special" character in the formula (i.e., similar to for example the gam package with the character "s" in y ~ s(x)). I've checked and it seems this is done through attr(,"specials"). However, the section of code below (as an example extracted from the gam package) gives me an error as shown at

Details in documentation: "All of ?weights?, ?subset?, ?offset?, ?etastart? and ?mustart? are evaluated in the same way as variables in ?formula?, that is first in ?data? and then in the environment of ?formula?." In fact, `data` is usually not an environment, and I have not seen arguments evaluated in `environment(formula)` when `data` is provided. (Information in `environment(formula)`

Bug summary: glm() causes a segfault if the argument 'data' is a data frame with more than 16384 rows. Bug demonstration: -------input --------------- N <- 16400 df <- data.frame(x=runif(N, min=1,max=2),y=rpois(N, 2)) glm(y ~ x, family=poisson, data=df) ------ output --------------- *** caught segfault *** address (nil),

Hi everyone: I am just wondering how can I use weights with MCMClogit function (in MCMCpack package). For example, in case of glm function as given below, there is weights option in the arguments. Aparently there is no option of using weights in MCMClogit. glm(formula, family = gaussian, data, weights, subset, na.action, start = NULL, etastart, mustart, offset, control =

This is just a note/wishlist/for the record: With foo1 <- function() { res; } foo2 <- function() { for (i in c()) res <- 1; res; } foo3 <- function() { while (FALSE) res <- 1; res; } foo4 <- function() { if (FALSE) res <- 1; res; } we get: > foo1() Error in foo1() : object 'res' not found > foo2() Error in foo2() : object 'res' not

--fupGvOGOQM Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit There's a simple bug in the handling of the start and offset arguments in glm and glm.fit. The bug exists in the latest development version of R (version information below), but it appears that glm.R has not been touched much lately, so the bug affects at

Hello R Users, I am having difficulty deleting the last warning message in a loop so that the only warning that is produced is that from the most recent line of code. I have tried options(warn=1), rm(last.warning), and resetting the last.warning using something like: > warning("Resetting warning message") This problem has been addressed in a previous listserve string,

Hello R-users. I haven't use R for a life time and this might be trivial - I hope you do not mind. I have a questions about arguments in the Glm-function. There seems to be something that I cannot cope. The basics are ok: > y <- as.double(rnorm(20) > .5) > logit.model <- glm(y ~ rnorm(20), family=binomial(link=logit), trace = TRUE) Deviance = 28.34255 Iterations - 1

This is not so much a bug as an infelicity in the code that can easily be fixed. The initialize expression in the quasi family function is, (uniformly for all links and all variance functions): initialize <- expression({ n <- rep.int(1, nobs) mustart <- y + 0.1 * (y == 0) }) This is inappropriate (and often fails) for variance function "mu(1-mu)".