search for: xlevs

I am trying once again. By just changing f <- match(xlevs[f], nlevs) to f <- match(xlevs, nlevs)[f] , function 'factor' in R devel could be made more consistent and back-compatible. Why not picking it? -------------------------------------------- On Sat, 25/11/17, Suharto Anggono Suharto Anggono <suharto_anggono at yahoo.com> wrote: Su...

Dear r-devel list members, I'm posting this message here because it concerns the nlme package, which is maintained by R-core. The problem I'm about to describe is somewhere between a bug and a feature request, and so I thought it a good idea to ask here rather posting a bug report to the R bugzilla. I was made aware (by Ben Bolker) that the car::Anova() method for "lme"

Over a decade ago there was a problem with model.frame when the variable names were long: https://stat.ethz.ch/pipermail/r-help/2002-August/024492.html I have similar symptoms with R 2.15.3 on Windows 7: Browse[2]> x <- model.matrix(formula(myform), p$data) Error in model.frame.default(object, data, xlev = xlev) (from mice.R#601) : object is not a matrix My attempt at a work-around

...devel, I saw attempts to speed up subsetting and 'match', and to cache results of conversion of small nonnegative integers to character string. That's good. I am sorry for pushing, still. Is the partial new behavior of function 'factor' with respect to NA really worthy? match(xlevs, nlevs)[f] looks nice, too. - Using f <- match(xlevs, nlevs)[f] instead of f <- match(xlevs[f], nlevs) for remapping - Remapping only if length(nlevs) differs from length(xlevs) Applying changes similar to above to function 'levels<-.factor' will not change 'levels<-.facto...

# r-bugs@r-project.org `predict' complains about new factor levels, even if the "new" levels are merely levels in the original that didn't occur in the original fit and were sensibly dropped, and that don't occur in the prediction data either. (At least if `drop.unused.levels' was set to TRUE, which the default.) test> scrunge.data.2_ data.frame( y=runif( 3),

Dear list members, After further testing, I found that the following simplified version of model.matrix.lme(), which omits passing xlev to the default method, is more robust. The previous version generated spurious warnings in some circumstances. model.matrix.lme <- function(object, ...){ data <- object$data if (is.null(data)){ NextMethod(formula(object),

Dear DevelopeRs, in continuing with my suite of packages on experimental design, I am stuck with an issue that appears to be related to package AlgDesign - I have tried to get it solved by Bob Wheeler, but he seems to be stuck as well. Whenever AlgDesign is loaded, some of my code does not work any more. For example, in a fresh R session: require(DoE.base) fac.design(nlevels=c(2,6,2))

Hi, I'm trying to get sparse.model.matrix to retain unused levels. I can't seem to get this working through the most obvious routes such as specifying drop.unused.levels = FALSE in the model.frame or trying to pass all levels in xlev,which is an argument to sparse.model.matrix (see code below). Any help would be gratefully received. Cheers, Jarrod fac<-factor(rep(1:10,10),

I'm working on predict.survreg and am confused about xlevels. The model.frame method has the argument, but none of the standard methods (model.frame.lm, model.frame.glm) appear to make use of it. The documentation for model.matrix states: xlev: to be used as argument of model.frame if data has no "terms" attribute. But the terms attribute has no xlevels information in it, so I

I think there are two bugs in aov() that shows up when the right hand side of `formula' contains both `-1' and an Error() term, e.g., aov(y ~ a + b - 1 + Error(c), ...). Without `-1' or `Error()' there is no problem. I've included and example, and the source of aov() with suggested fixes below. The first bug (labeled BUG 1 below) creates an extra, empty stratum inside

Full_Name: Glenn Stone Version: 1.5.1 and 1.6.0 OS: win2000 Submission from: (NULL) (168.140.227.9) The following code produces incorrect fitted values in version 1.5.1 and an error in 1.6.0 Error in "contrasts<-"(*tmp*, value = "contr.treatment") : contrasts apply only to factors In addition: Warning message: variable ihalf is not a factor in:

My idea (like in https://bugs.r-project.org/bugzilla/attachment.cgi?id=1540 ): - For remapping, use f <- match(xlevs, nlevs)[f] instead of f <- match(xlevs[f], nlevs) (I have mentioned it). - Remap only if length(nlevs) differs from length(xlevs) . On use of 'order' in function 'factor' in R devel, factor.Rd still says 'sort.list' in "Details" section. My comments on the pa...

I believe you are right, but can you please explain why anyone would want to fit this model? It differs only in the coding from aov(y ~ a + b + Error(c), data=test.df) and merely lumps together the top two strata. There is a much simpler fix: in the line if(intercept) nmstrata <- c("(Intercept)", nmstrata) remove the condition (and drop the empty stratum later if you

Hi all, I''m still not quite happy with the NA and factor handling of lm and predict.lm in R1.6.1 (forcing me to use my not very skillfully crafted patches). Here is the problem 1: >

Seems to be a day for finding peculiar little things. There is an inconsistency in the behavior of lm vis a vis glm: > x <- rnorm(15) > y <- 1 + 10*x + rnorm(15) > z <- as.factor(rep(c("A","B","C"),rep(5,3))) > xyz <- data.frame(x,y,z) > fit.lm <- lm(y ~ x + z, data=xyz, subset=(z != "C")) > fit.glm <- glm(y ~ x +

When I alter the levels of a factor, why does it alter the names too? f <- factor(c(A="one",B="two",C="one",D="one",E="three"), levels=c("one","two","three")) names(f) -- gives [1] "A" "B" "C" "D" "E" levels(f) <-

Hello, I have tried reading the documentation and googling for the answer but reviewing the online matches I end up more confused than before. My problem is apparently simple. I fit a glm model (2^k experiment), and then I would like to predict the response variable (Throughput) for unseen factor levels. When I try to predict I get the following error: > throughput.pred <-

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1133331701-635408861-993124011=:10449 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm not sure if the warning messages Warning messages: 1: variable 67 is not a factor in:

There is a bug in `predict' whereby the order of variables sometimes gets re-arranged compared to the original fit, and then disaster results. Specifically, the 'variables' and 'predvars' attributes of a 'terms' object get out of synch. This only happens when the terms in the original formula get re-ordered during fitting: test> scrunge.data_ data.frame(

Hi All, I'm a newbie and have two questions. Please pardon me if they are very basic. 1. I'm using a regression tree to predict the selling prices of 10 new records (homes). The following code is resulting in an error message: pred <- predict(model, newdata = outOfSample[, -6]) The error message is: Error in model.frame.default(Terms, newdata, na.action = na.action, xlev =