similar to: termplot (PR#2687)

Displaying 20 results from an estimated 1000 matches similar to: "termplot (PR#2687)"

2004 Mar 18
1
termplot has problems with a single term (fix included) (PR#6679)
On Thu, 18 Mar 2004 k.hansen@biostat.ku.dk wrote: > The bug exists on R-1.9.0-alpha compiled the 10/3. > > Termplot has a problem if either the model only contains a single term > or if asked to plot a single term. In addition there are problems with > the option se = TRUE. I can't reproduce this in either R-devel or 1.8.1, and termplot hasn't changed since January. I do
2004 Mar 18
1
termplot has problems with a single term (fix included) (PR#6675)
The bug exists on R-1.9.0-alpha compiled the 10/3. Termplot has a problem if either the model only contains a single term or if asked to plot a single term. In addition there are problems with the option se = TRUE. Analysis: termplot starts with terms <- if (is.null(terms)) predict(model, type = "terms", se = se) else predict(model, type = "terms", se = se,
2004 Jan 04
0
termplot; failure to subset non-dataframe carriers (PR#6327)
termplot() does not carry subsetting over to carriers that are in the environment but not in the data frame. This generates a "subscript out of bounds" error. > data(ToothGrowth) > logdose <- log(ToothGrowth$dose) > tooth.lm <- lm(len ~ logdose, data=ToothGrowth) > termplot(tooth.lm) ## Works fine > toothVC2.lm <- lm(len ~ poly(dose,2),
2003 Mar 26
2
predict (PR#2685)
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(
2001 Jan 27
1
termplot fails for composite non-factor terms (PR#828)
I am running R 1.2.1 under Windows 98SE. termplot() currently fails when there are composite terms, thus: > library(mass) > data(hills) > hills.lm <- lm(time ~ climb + poly(dist, 2), data = hills) > termplot(hills.lm) Hit <Return> to see next plot: Error in eval(expr, envir, enclos) : Object "dist" not found The call >
2000 Oct 27
1
par(ask=T) in termplot() (PR#711)
At 11:57 25/10/00 +0100, Brian Ripley wrote: >> Date: mer., 25 oct. 2000 12:38:55 +0200 >> From: Emmanuel Paradis <paradis@isem.univ-montp2.fr> > >> I think it would be nice to have par(ask=T) set by default in termplot(), >> like it is in plot.lm(). > >Well, it isn't really the default in plot.lm, the default for `ask' being > >interactive()
2004 Dec 06
0
a better "source(echo=TRUE)" {was "....how to pause...."}
You might want to have a look at 'source.mvb' & friends in the 'mvbutils' package. It's designed to allow control of nested sourcing, and to allow interspersed data and commands in a single self-contained file. Unlike 'source', 'source.mvb' reads each statement and immediately executes it, before proceeding to the next; hence it has do the parsing to figure
2002 Apr 18
2
Changing tick mark labels
Hello, Can anyone help me out with this problem? After performing logistic regressions and testing the significance with likelihood ratios, I have plotted the results using "termplot". I am wondering, how to get the names of my variables to appear on the x-axis rather than ascending numbers? I have used: termplot(fm, se=T, axes=FALSE, col.se="black") axis(1, 1:4,
2003 Mar 26
5
predict (PR#2686)
# 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),
2003 Aug 05
1
(PR#3658)
The function 'getAnywhere' crashes if given a non-existent name containing a period: > getAnywhere( 'nomethod.noclassforme') Error in get(x, envir, mode, inherits) : variable "nomethod" was not found However, 'getAnywhere' behaves gracefully if the non-existent name lacks a period: > getAnywhere( 'nomethod') no object named `nomethod' was
2002 Dec 27
0
parse and pushBack (PR#2396)
Is this the last bug of the year? Well, it's the last one from me, anyway... The "parse" function seems to give erratic behaviour when used in conjunction with "pushBack" on an open connection (R1.6.1, Windows 2000). Try this: > { cat( c( '1', 'a+b', '2'), file='r123.r', sep='\n'); tcon_ file( 'r123.r'); open( tcon);
2003 Oct 28
0
data.frame replacement (PR#4820)
When replacing all elements of a column in a data.frame, a corrupt data.frame will be generated if the replacer is "short": test> bbb <- data.frame( x=1:2) test> bbb[,'x'] <- 3 # should fill the column test> bbb x 1 3 2 <NA> Warning message: corrupt data frame: columns will be truncated or padded with NAs in: format.data.frame(x, digits = digits)
2000 Oct 25
2
par(ask=T) in termplot()
Hi, I think it would be nice to have par(ask=T) set by default in termplot(), like it is in plot.lm(). Best, Emmanuel Paradis -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !)
2003 Sep 25
1
tkinsert (PR#4289)
In R-1.7.1, I used to be able to append a character vector to a 'tklistbox' with e.g. listio <- tklistbox( tktoplevel(), font='Courier', height=20, width=20, setgrid=TRUE) tkinsert( listio, 'end', letters[1:3]) tkpack( listio,side='left', expand=TRUE, fill='both') and three items would be added to 'listio'. This doesn't work in R-devel-- it
2016 Dec 12
0
[RE: why does parent.frame() cycle when called from inside capture.output()?]
Thanks, Mark - I'm taking up your invitation to forward your message to the list just because it gives us some valuable data on (1) how long the behavior has been around, and (2) how many other people (don't) understand the behavior, and (3) how we might fix or work around it. I notice some other people also seem to be diffident about posting on R-devel; perhaps I should conclude that
2003 Dec 16
0
Help w/ termplot & predict.coxph/ns
I am fitting a cox PH model w/ 2 predictors, x1 = 0/1 treatment variable and x2=continuous variable. I am using natural splines (ns) to model the effect of x2. I would like to examine the estimated effect of x2 on the hazard. I have tried various approaches (below; let model.fit= fitted model using coxph in survival library): 1. The simplest method appears to be using termplot(model.fit).
2004 Jan 22
1
Bug in termplot?
Hi, Is this a bug in termplot, or (once again) do I just not understand what R is really doing? I am using termplot to contruct partial residual plots, 1. For all terms at once 2. One term at a time but I get different results from these two methods. To give a concrete example, I would have thought the top and bottom rows of the plot constructed with the following code would be identical.
2012 Oct 19
1
Addition of plot=F argument to termplot
I have a suggested addition to termplot. We have a local mod that is used whenever none of the termplot options is quite right. It is used here almost daily for Cox models in order to put the y axis on a risk scale: ---- fit <- coxph(Surv(time, status) ~ ph.ecog + pspline(age), data=lung) zz <- termplot(fit, se=TRUE, plot=FALSE) yy <- zz$age$y + outer(zz$age$se, c(0, -2, 2),
2009 Oct 16
0
post-installation startup problem with 2.10.0
I've just installed R2.10.0 v50082, and found the problem described below the first few times I launched it. Did not occur with v49613 (the previous most recent version I have). The problem has now gone away, and is therefore non-reproducible, but there seems to be something up with parameter processing or environment variable checking or loading of .RData files immediately after installation.
2009 Oct 19
0
weird warning in [.data.frame with 2.10
I'm getting the following warnings under 2.10 v50082 but not v49613 >> In addition: Warning messages: 1: In `[.data.frame`(df, -(1:nrow(df)), , drop = FALSE) : named arguments other than 'drop' are discouraged 5: In `[.data.frame`(object, !omit, , drop = FALSE) : >> named arguments other than 'drop' are discouraged In neither case are there any named arguments,