similar to: Namespace problem

I'm trying to learn how to use namespaces, so I have created a small package with two functions. My NAMESPACE file is importFrom(survival, Surv) export(mlreg.fit, risksets) because 'mlreg.fit' uses 'Surv' from 'survival'. However I get * checking package dependencies ... WARNING Namespace dependencies not required: survival Why? (If I remove 'importFrom' I

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 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 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

Dear all, How can I analyze a life table (e.g. for a cohort of insects) in R? I have 20 insects in 200 cages with two different treatments, whose survival is followed over time, such that, e.g., in one treatment, the number of animals surviving is c(20,18,16,12,10,8,4,0), while in the other treatment the survival is c(20,20,18,18,16,15,15,14) at 8 subsequent time intervals. I would very

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

Dear all, I am trying to wrap up a package. On entering R CMD check, I get the following error messages: [...] * checking S3 generic/method consistency ... WARNING Error in .try_quietly({ : Error in library(package, lib.loc = lib.loc, character.only = TRUE, verbose = FALSE) : package/namespace load failed for 'resper' Execution halted See section 'Generic functions and methods'

Hi, I'm using rw2000dev.exe (Win32) built on August 14. If this isn't already planned, can I suggest that when checkS3methods() (called by R CMD check) fails because of a syntax error in a dependent package listed in the DESCRIPTION file of the main package being checked, it would be nice if checkS3methods() reported which dependent package caused it to fail? Running R CMD check on my

Hello, I wrote a library which seems to work on my PC, and on different Unix systems. As it is written in the "Writing R Extensions" manual, I execute a R CMD check on my library. I have always the same errors messages: * checking S3 generic/method consistency ... WARNING Error in .try_quietly({ : Error in library(package, lib.loc = lib.loc, character .only = TRUE,

? stato filtrato un testo allegato il cui set di caratteri non era indicato... Nome: non disponibile Url: https://stat.ethz.ch/pipermail/r-help/attachments/20060627/84d9bd54/attachment.pl

I noticed the same thing as I reported below, when I upgraded from R-2.0.0-alpha-20040918 to today's beta version: 'R CMD check' failed as before; but after cleaning 'src' from .o and .so files, it worked again. So the two-day-old '.so' file is obviously different from today's. Has compiler directives changed in the two last days? Or what is happening? G?ran On

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,

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

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

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() {

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

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: ****

Thanks: I installed from source and got an error when loading a package: -------------------------------------------------------------------- > library(eha) Loading required package: survival Error: package or namespace load failed for ?eha? in dyn.load(file, DLLpath = DLLpath, ...): unable to load shared object '/usr/local/lib/R/site-library/eha/libs/eha.so':

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