similar to: lm documentation, "formula" component (PR#1105)

Displaying 20 results from an estimated 10000 matches similar to: "lm documentation, "formula" component (PR#1105)"

2010 Nov 29
1
extracting P values from lm model
Hello I am trying to get out of an lm model the fstatistics, however after I run the model I write > names(Model) and the fstatistic does not appear only these. names(Model) [1] "coefficients" "residuals" "effects" "rank" "fitted.values" [6] "assign" "qr" "df.residual"
2019 Aug 30
3
inconsistent handling of factor, character, and logical predictors in lm()
Dear R-devel list members, I've discovered an inconsistency in how lm() and similar functions handle logical predictors as opposed to factor or character predictors. An "lm" object for a model that includes factor or character predictors includes the levels of a factor or unique values of a character predictor in the $xlevels component of the object, but not the FALSE/TRUE values
2003 Apr 23
3
regression parms var-cov matrix
Win2k, R1.6.2. I've been using Splus 6.1 and wanted to try the same regression analysis in R. Using "names( blah.lm )" in R yields [1] "coefficients" "residuals" "effects" "rank" [5] "fitted.values" "assign" "qr" "df.residual" [9] "xlevels"
2019 Aug 31
2
inconsistent handling of factor, character, and logical predictors in lm()
Dear Abby, > On Aug 30, 2019, at 8:20 PM, Abby Spurdle <spurdle.a at gmail.com> wrote: > >> I think that it would be better to handle factors, character predictors, and logical predictors consistently. > > "logical predictors" can be regarded as categorical or continuous (i.e. 0 or 1). > And the model matrix should be the same, either way. I think that
2011 Sep 09
4
Very simple question about list components
I have a list 'ans' from the following code: tt <- rnorm(50) rr <- rnorm(50) ans <- lm(rr~tt) ans[1] is "$coefficients", ans[2] is "$residuals", ans[3] is "$effects", ... and so on up to ans[12]. Is there an easy way to display just these names and not the data they contain? I thought I saw my advisor type "ans$" and they were displayed,
2011 Apr 19
1
How to Extract Information from SIMEX Output
Below is a SIMEX object that was generated with the "simex" function from the "simex" package applied to a logistic regression fit. From this mountain of information I would like to extract all of the values summarized in this line: .. ..$ variance.jackknife: num [1:5, 1:4] 1.684 1.144 0.85 0.624 0.519 ... Can someone suggest how to go about doing this? I can extract the
2006 Mar 27
1
Glm poisson
Hello, I am using the glm model with a poisson distribution. The model runs just fine but when I try to get the null deviance for the model of the null degrees of freedom I get the following errors: > null.deviance(pAmeir_1) Error: couldn't find function "null.deviance" > df.null(pAmeir_1) Error: couldn't find function "df.null" When I do: >
2002 Jan 22
1
documentation and plotting with lqs
Dear r-help, Is there any available description of the components of lqs objects found in the package "lqs"? > names(slts) [1] "crit" "sing" "coefficients" "bestone" [5] "fitted.values" "residuals" "scale" "terms" [9] "call"
2018 Mar 16
2
Apparent bug in behavior of formulas with '-' operator for lm
Dear R-developers, In the 'lm' documentation, the '-' operator is only specified to be used with -1 (to remove the intercept from the model). However, the documentation also refers to the 'formula' help file, which indicates that it is possible to subtract any term. Indeed, the following works with no problems (the period '.' stands for 'all terms except the
2006 Oct 12
2
how to get the variance-covariance matrix/information of alpha and beta after fitting a GLMs?
Dear friends, After fitting a generalized linear models ,i hope to get the variance of alpha,variance of beta and their covariance, that is , the variance-covariance matrix/information of alpha and beta , suppose *B* is the object of GLMs, i use attributes(B) to look for the options ,but can't find it, anybody knows how to get it? > attributes(B) $names [1] "coefficients"
2017 Jun 15
2
duplicated factor labels.
Dear R devel I've been wondering about this for a while. I am sorry to ask for your time, but can one of you help me understand this? This concerns duplicated labels, not levels, in the factor function. I think it is hard to understand that factor() fails, but levels() after does not > x <- 1:6 > xlevels <- 1:6 > xlabels <- c(1, NA, NA, 4, 4, 4) > y <- factor(x,
2018 Mar 08
0
Names of variables needed in newdata for predict.glm
Hi, Some try: > names(mi$xlevels) [1] "f" > all.vars(mi$formula) [1] "D" "x" "f" "Y" > names(mx$xlevels) [1] "f" > all.vars(mx$formula) [1] "D" "x" "f" When offset is indicated out of the formula, it does not work... Marc Le 07/03/2018 ? 06:20, Bendix Carstensen a ?crit?: > I would like
2009 Aug 21
1
problem with plot.lm?
I'm bringing this issue to r-devel as my idea of sending it to r-help appears to be wrong. The following is reproducible in R-patched and R-devel (also in older versions). An outlier is inserted in group E and the last plot by plot.lm suggests that the point belongs to D. It appears to me that: * (facval, rsp) and * x$xlevels[[1L]][order(sapply(split(yh,mf[,1]), mean))] are sorted
2004 Jun 09
2
Specifying xlevels in effects library
library(effects) mod <- lm(Measurement ~ Age + Sex, data=d) e <-effect("Sex",mod) The effect is evaluated at the mean age. > e Sex effect Sex F M 43.33083 44.48531 > > e$model.matrix (Intercept) Age SexM 1 1 130.5859 0 23 1 130.5859 1 To evaluate the effect at Age=120 I tried: e
2002 Feb 04
2
ASCII characters: from decimal code to R octal?
Is there a straightforward way to convert character information from decimal representation to the octal one used by R? I'd like something like a function ascii(number,base=10), such that > ascii(91) [1] "\133" I can easily do the mapping from 91 to 133, but what is a good way to operate on 133 to deliver "\133"? Would a lookup table be a better solution? David
2004 Jun 14
0
inheritance problem in multcomp package (PR#6978)
# Your mailer is set to "none" (default on Windows), # hence we cannot send the bug report directly from R. # Please copy the bug report (after finishing it) to # your favorite email program and send it to # # r-bugs@r-project.org # ###################################################### The multcomp functions work on "lm" objects as anticipated. They do not work on
2011 Jun 14
1
Expand DF with all levels of a variable
Dear list, I would like to expand a DF with all the missing levels of a variable. a <- c(2,2,3,4,5,6,7,8,9) a.cut <- cut(a, breaks=c(0,2,6,9,12), right=FALSE ) (x <- data.frame(a, a.cut)) # In 'x' the level "[0,2)" is "missing". AddMissingLevel <- function(xdf) { xfac <- factor( c("[0,2)", "[2,6)", "[6,9)",
2011 Mar 23
1
predict.lm How to introduce new data?
Dear all, I've fitted a lm using 61 data (training data), and I'left 10 as test data. Training data and test data are stored in an excell. training <- read.xls("C:/...../training.xls") , the same for test. That is: v1 v2 ... v15 When I type str(training) and str(test), both sets have the same names The resulting model is lms <- lm(vd ~ log(v1) + fv2+ fv5+ fv7 )
2012 Feb 25
1
Unexpected behavior in factor level ordering
Hello, Everybody: This may not be a "bug", but for me it is an unexpected outcome. A factor variable's levels do not retain their ordering after the levels function is used. I supply an example in which a factor with values "BC" "AD" (in that order) is unintentionally re-alphabetized by the levels function. To me, this is very bad behavior. Would you agree? #
2011 Mar 30
1
Using xlevels
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