similar to: vcov.nlminb

Displaying 20 results from an estimated 2000 matches similar to: "vcov.nlminb"

2004 Oct 26
2
vcov method for 'coxph' objects
Dear all, The help file for the generic function vcov states "Classes with methods for this function include: 'lm', 'glm', 'nls', 'lme', 'gls', 'coxph' and 'survreg' (the last two in package 'survival')." Since, I am not able to use vcov.coxph(), I am wondering whether I am missing something (as I suspect..) regards, vito
2004 Oct 06
4
R2.0.0 bug in function vcov in library survival (PR#7266)
Full_Name: Sven Sandin Version: 2.0.0 OS: SuSE Linux 9.0 Submission from: (NULL) (81.227.17.135) Have just compiled and installed R-2.0.0.tar.gz running SuSE9.0. The function vcov do not accept "coxph" object as input any longer. The same R-program running R1.9.1 do work. R-program attached below. Exporting the coxph object from R2.0.0 to R1.9.1 I get vcov ouput in R1.9.1. Exporting
2004 Nov 19
2
function 'vcov' for coxph in R 2.0.0
Hi there, After I fitted a cox model, I used vcov to obtain the variance of the parameter estimate. It worked correctly in R 1.9.1. But it failed in R 2.0.0 and the error message is Error in vcov(cox.1) : no applicable method for "vcov" I don't know if it is a bug or there is some update on this function. Thanks! Lei Liu Assistant Professor Division of Biostatistics and
2009 Jan 08
1
VCOV Source Code
Dear R Help, I wonder the way to show the source code of [vcov] command. Usually, it can show the source code after input the command and enter. But for [vcov], it shows function (object, ...) UseMethod("vcov") <environment: namespace:stats> I appreciate for your help. Best wishes. Christina [[alternative HTML version deleted]]
2009 May 20
1
Error with regsubset in leaps package - vcov and all.best option (plus calculating VIFs for subsets)
Hi all I am hoping this is just a minor problem, I am trying to implement a best subsets regression procedure on some ecological datasets using the regsubsets function in the leaps package. The dataset contains 43 predictor variables plus the response (logcount) all in a dataframe called environment. I am implementing it as follows: library(leaps)
2006 Aug 21
1
"vcov" error in svyby and svytable functions
Hi, I'm trying to compute survey svytable statistic on subsets by using the svyby function. Here is the code: b<-svyby(~V024+V751, by=~V025, design=strat2, svytable, round=TRUE) The vars, V024, V751 and V025 are factors. The by var has 2 levels, and hence there will be two subsets. strat2 is created by the svydesign function. It's giving me the following error: >
2004 Sep 27
1
Funny behaviour of coef() and vcov() if X is singular
coef() and vcov() have different dimensions if a model contains alised parameters as the following example illustrates. A search on "alised" gave noting as far as I could see. Is this a known bug? Bendix C ---------------------- Bendix Carstensen Senior Statistician Steno Diabetes Center Niels Steensens Vej 2 DK-2820 Gentofte Denmark tel: +45 44 43 87 38 mob: +45 30 75 87 38 fax: +45
2017 Nov 02
2
vcov and survival
>>>>> Fox, John <jfox at mcmaster.ca> >>>>> on Thu, 14 Sep 2017 13:46:44 +0000 writes: > Dear Martin, I made three points which likely got lost > because of the way I presented them: > (1) Singularity is an unusual situation and should be made > more prominent. It typically reflects a problem with the > data or the
2005 Feb 25
1
vcov on result of rlm() yields "-- please report!" (PR#7707)
Dear r-bugs, I looked over the FAQ. Hope I'm reporting this correctly. I ran this on both solaris and windows. I've provided terminal snapshots which include how R was called from the command line, and the result of version at the R prompt. I have attached the .r file, and the data file and the output snapshots. Below also find everything except only a few lines of the data file. Note
2017 Sep 13
3
vcov and survival
Dear Terry, Even the behaviour of lm() and glm() isn't entirely consistent. In both cases, singularity results in NA coefficients by default, and these are reported in the model summary and coefficient vector, but not in the coefficient covariance matrix: ---------------- > mod.lm <- lm(Employed ~ GNP + Population + I(GNP + Population), + data=longley) >
2017 Sep 14
6
vcov and survival
>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Thu, 14 Sep 2017 10:13:02 +0200 writes: >>>>> Fox, John <jfox at mcmaster.ca> >>>>> on Wed, 13 Sep 2017 22:45:07 +0000 writes: >> Dear Terry, >> Even the behaviour of lm() and glm() isn't entirely consistent. In both cases,
2008 Nov 23
2
Need help: Loading a large data set.
Hi All, I am dealing with a large data set which translates in to a sparse matrix, I want to load this data that is spread in approximately 17000+ files each defining a row and each file has variable number of records that come with its column number and the value that they store. I wish to load this data in memory from these files one by one. Is there anyway I can do this in R, before I start
2009 Nov 24
0
can't use function vcov with a GAMLSS object??
Hi everyone, I''m trying to use function vcov to extract the covariance matrix from a GAMLSS object. But I''m getting some strange errors and I was hoping someone could help me out? Vcov works with the same model for lm and glm objects, but not gamlss objects. I''ve searched various help sites to no avail. Its very possible the reason is that vcov failed though,
2017 Nov 07
0
New vcov(*, complete=TRUE) etc -- coef(<lm>) vs coef(<aov>)
Dear Martin, I think that your plan makes sense. It's too bad that aov() behaved differently in this respect from lm(), and thus created more work, but it's not be a bad thing that the difference is now explicit and documented. I expect that that other problems like this will surface, particularly with contributed packages (and I know that you're aware that this has already happened
2017 Sep 14
0
vcov and survival
Dear Terry, It's not surprising that different modeling functions behave differently in this respect because there's no articulated standard. Please see my response to Martin for my take on the singular.ok argument. For a highly sophisticated user like you, singular.ok=TRUE isn't problematic -- you're not going to fail to notice an NA in the coefficient vector -- but I've
2012 Jul 04
2
About nlminb function
Hello I want to use the nlminb function but I have the objective function like characters. I can summarize the problem using the first example in the nlminb documentation. x <- rnbinom(100, mu = 10, size = 10) hdev <- function(par) -sum(dnbinom(x, mu = par[1], size = par[2], log = TRUE)) nlminb(c(9, 12), objective=hdev) With the last instructions we obtain appropriate results. If I have
2017 Sep 14
0
vcov and survival
>>>>> Fox, John <jfox at mcmaster.ca> >>>>> on Wed, 13 Sep 2017 22:45:07 +0000 writes: > Dear Terry, > Even the behaviour of lm() and glm() isn't entirely consistent. In both cases, singularity results in NA coefficients by default, and these are reported in the model summary and coefficient vector, but not in the coefficient covariance
2012 Nov 04
1
Struggeling with nlminb...
Hallo together, I am trying to estimate parameters by means of QMLE using the nlminb optimizer for a tree-structured GARCH model. I face two problems. First, the optimizer returns error[8] false convergence if I estimate the functions below. I have estimated the model at first with nlm without any problems, but then I needed to add some constraints so i choose nlminb.
2008 Dec 03
1
nlminb: names of parameter vector not passed to objective function
Dear R developers, I tried to use nlminb instead of optim for a current problem (fitting parameters of a differential equation model). The PORT algorithm converged much better than any of optim's methods and the identified parameters are plausible. However, it took me a while before spotting the reason of a technical problem that nlminb, in contrast to optim, does not pass names of the
2017 Sep 14
0
vcov and survival
Dear Martin, I made three points which likely got lost because of the way I presented them: (1) Singularity is an unusual situation and should be made more prominent. It typically reflects a problem with the data or the specification of the model. That's not to say that it *never* makes sense to allow singular fits (as in the situations you mentions). I'd favour setting