search for: ehas

Dear List, After including cluster() option the coxreg (from eha package) produces results slightly different than that of coxph (from survival) in the following time-dependent treatment effect calculation (example is used just to make the point). Will appreciate any explaination / comment. cheers, Ehsan ############################ require(survival) require(eha) data(heart) # create weights

When I try 'install-packages' (from menu) in R-1.7.0 (Windows), I get > install.packages(choose.files('',filters=Filters[c('zip','All'),]), .libPaths()[1], CRAN = NULL) Error in file(file, "r") : unable to open connection In addition: Warning message: cannot open file `eha060/DESCRIPTION' > but it works with R-1.6.2. It also works if I

A few days ago I uploaded to CRAN a new package called 'eha', which stands for 'Event History Analysis'. Its main focus is on proportional hazards modeling in survival analysis, and in that respect eha can be regarded as a complement and an extension to the 'survival' package. In fact eha requires survival. Eha contains three functions for proportional hazards

A few days ago I uploaded to CRAN a new package called 'eha', which stands for 'Event History Analysis'. Its main focus is on proportional hazards modeling in survival analysis, and in that respect eha can be regarded as a complement and an extension to the 'survival' package. In fact eha requires survival. Eha contains three functions for proportional hazards

As stated in the design paragraph, this design does not intend to model precise CFG at instruction level since it’s complicated and unnecessary. As long as we comply C and C++ rules listed below, we achieve -EHa semantic. There is NO need to precisely model HW exception control flow at instruction-level. Your example about memcpy() is just a bug in current implementation. I will fix it so that

Dear R-users, I need to use the aftreg function in package 'eha' to estimate failure times for left truncated survival data. Apparently, survreg still cannot fit such models. Both functions should be fitting the accelerated failure time (Weibull) model. However, as G?ran Brostr?m points out in the help file for aftreg, the parameterisation is different giving rise to different

I am unsure what is being returned, and what is supposed to be returned, when using 'predict' with "type='expected'" for an aftreg survival model. The code below first generates a weibull model, then uses predict to create a vector of the linear predictors, then attempts to create the 'expected' vector, which is empty. The final two steps in the code generate a

Hi, This is a spin-off of previous Windows SEH RFC below. This RFC only focus on supporting HW Exception Handling. A detailed implementation can be seen in here: https://github.com/tentzen/llvm-project/commit/8a2421c274b683051e456cbe12c177e3b934fb5e It passes all MSVC SEH suite (excluding those with “Jumping out of _finally” ( _Local_Unwind)). Thanks, --Ten **** The rules for C code: ****

Hi list! I'm getting an error message when trying to fit an accelerated failure time parametric model using the aftreg() function from package eha: > Error in optim(beta, Fmin, method = "BFGS", control = list(trace = > as.integer(printlevel)), : > non-finite finite-difference value [2] This only happens when adding four specific covariates at the same time in the

Hi, Eli, Why are you under the impression that threw_exception() will not be called if optimizations are enabled? I don’t know if the -EHa Spec is clearly described in MSFT Webs. At least this proposal has described the rules for both C & C++ code. The very first rule clearly said that “no exception can move in or out of _try region., i.e., no potential faulty instruction can be moved

This kind of error seems to surprise R users. It surprises me that it doesn't happen much more frequently. The "BFGS" method of optim() from the 1990 Pascal version of my book was called the Variable Metric method as per Fletcher's 1970 paper it was drawn from. It really works much better with analytic gradients, and the Rvmmin package which is an all-R version that adds bounds

Dear mailing list, I'm trying to run the sample program about coxreg in the eha package. But the command is not recognized. I tried the boot and also the survival library. Hope you can help me solve this little problem. Thank you. Jei ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. University of the

Hello, Has anyone Knowledge about softphone IAX for pocket PC totally free? Tkanks for all. -- Sandra Salmer?n Ntutumu <makevuy@ehas.org> Tlf. Analog: +34 914888405 / M?vil: 653574298 Tlf. IP desde FWD: 656212. Ext: 10 / Tel. IP desde EHAS: 010010 Fundaci?n EHAS: Enlace Hispanoamericano de Salud - www.ehas.org Telemedicina rural para zonas aisladas de pa?ses en desarrollo

Hello everyone, I was wondering what is the status regarding exceptions for the windows-msvc target? The corresponding part of the documentation (llvm/decs/ExceptionHandling.rst) hasn't been updated since 2015, was there any progress since? This is most likely known, but there's significant divergence between the behavior of MSVC cl.exe and clang-cl.exe: Consider: void crash() {

A new version of 'eha' (0.92-1) is now on CRAN. From the ChangeLog: 0.92-1 (January 7, 2004) * mlreg: Geometric distribution (i.e., constant baseline discrete hazard) added. Not for frailty models, yet (on the TODO list). * mlreg: New argument, 'n.points', added to 'control'. Controls the number of points used in the Gauss-Hermite quadrature. * mlreg: Stricter

A new version (0.96.3) of the package 'eha' is now on CRAN. Apart from some bug fixes, there are some news. The most noteworthy are: (i) 'plot.Surv' has a few new options, (ii) 'weibreg' now can fit null models (i.e., only scale and shape) and covariates are no longer automatically centered (although this is still the default), (iii) there is a new function,

A new version of 'eha' (0.92-1) is now on CRAN. From the ChangeLog: 0.92-1 (January 7, 2004) * mlreg: Geometric distribution (i.e., constant baseline discrete hazard) added. Not for frailty models, yet (on the TODO list). * mlreg: New argument, 'n.points', added to 'control'. Controls the number of points used in the Gauss-Hermite quadrature. * mlreg: Stricter

Dear useRs, I am currently fitting an advanced failure time model using G?ran Brostr?m's excellent "eha" library with the "aftreg" command. My question: How do I interpret the "Overall p-value", that is reported at the very bottom of the output? I already figured out it must be a chi-square test, but I am wondering what a p-value < 0.01 means: Does it mean

"Error in predict.coxph(f.ph.eha, newdata = mort, type = "lp") : Data is not the same size as it was in the original fit" This error message was added in a recent update to predict.coxph. If it needs to reconstruct some aspects from the original fit, such as the X matrix or strata vector, it makes sure that the data set is the same size. It was to stop fit <-

Now I try to add some C and Fortan code to my package, so the NAMESPACE file is useDynLib(eha) importFrom(survival, Surv) export(mlreg.fit, risksets) but I get ..... * checking R files for library.dynam ... OK * checking S3 generic/method consistency ... WARNING Error in .try_quietly({ : Error in library(package, lib.loc = lib.loc, character.only = TRUE, verbose = FALSE) :