similar to: package development

Based on the feedback received, I did the following: a) moved my lib sub-directory from the existing installed R version to c:\myRLib b) installed the updated R version c) created .Renviron file in the home directory (C:\R-2.5.1) with the line R_LIBS=c:/myRLib d) used .libPaths() command to confirm that the new R installation was recognizing the myRLib sub-directory e) deleted my old R

Dear all, Please, please I really need your help, since I am not able to solve the problem myself: It seems that until now most Windows users of my Bioconductor package "xps" use Windows XP, but recently a user tried to use it on Windows Vista where it crashed R immediately. Since I assume that some users may migrate to the upcoming Windows 7 where the problem will be the same, I

Hello I use the function .libPaths() > .libPaths() [1] "/usr/local/lib/R/library" > .libPaths(c("/usr/local/lib/myRlib","/usr/local/lib/library")) > .libPaths() [1] "/usr/local/lib/R/library" but it simply does not pick up the new path. Can anybody help? (The problem originates from the inability to install packages into

Hi, First: sorry for my bad English! I have received several emails reporting problems using Tinn-R with the new R version (2.11.0). This email is meant to assist the users. This problem is new and is related with R 2.11.0 and Hmisc package for Windows! After download and install R 2.11.0pat under Linux and Windows, see below my results: a) Under Linux (Open SUSE 11.3) - I found no problem

The survival package makes significant use of the "specials" argument of terms(), before calling model.frame; it is part of nearly every modeling function. The reason is that strata argments simply have to be handled differently than other things on the right hand side. Likewise for tt() and cluster(), though those are much less frequent. I now get "bug reports" from the

When I run R CMD check on the survival package I invariably get a note: ... * checking for file ?survival/DESCRIPTION? ... OK * this is package ?survival? version ?3.2-6? * checking CRAN incoming feasibility ... NOTE Maintainer: ?Terry M Therneau <therneau.terry at mayo.edu>? ... This is sufficient for the auto-check process to return the following failure message: Dear maintainer,

I've created some Splus code for a microarray problem that - needed to be in C, to take advantage of some sparse matrix properties - uses a cholesky decompostion as part of the computation For the cholesky, I used the cholesky2 routine, which is a part of the survival library. It does just what I want and I'm familiar with it (after all, I wrote it). In Splus, this all works

I recently had a long argument wrt the survival package, namely that the following code didn't do what they expected, and so they reported it as a bug ? survival::coxph( survival::Surv(time, status) ~ age + sex + survival::strata(inst), data=lung) a. The Google R style guide? recommends that one put :: everywhere b. This breaks the recognition of cluster as a "special" in the

Hello, pointed to the article "Debugging Without (Too Many) Tears" of Mark Bravington in Rnews Vol 3/3, December 2003 there is a package mvbutils mentioned. So I started to install this package from within R > install.package(mvbutils) I receive an error essage that this package is not found! Is due to a merge,removal or rename of this package? When I try to follow this

> On Jun 1, 2019, at 12:59 PM, Peter Langfelder <peter.langfelder at gmail.com> wrote: > > On Sat, Jun 1, 2019 at 3:22 AM Therneau, Terry M., Ph.D. via R-devel > <r-devel at r-project.org> wrote: >> >> In the next version of the survival package I intend to make a non-upwardly compatable >> change to the survfit object. With over 600 dependent packages

Hello Colleagues, I've recently become a fan of Mark Bravington's mvbutils package for organizing analysis projects in a tree. Using cd(), Save(), fixr(), mlazy() etcetera solves nicely some of the nuisances that have worried or annoyed me and sometimes caused big problems over the years. Well thought out. Now one feature that would be fabulous would be automatic time-stamping of

In my genridge package, I define a function ridge() for ridge regression, creating objects of class 'ridge' that I intend to enhance. In a documentation example, I want to use some functions from the car package. However, that package requires survival, which also includes a ridge() function, for coxph models. So, once I require(car) my ridge() function is masked, which means I have to

A user asked me about this and I can't figure it out. tmt% R R Under development (unstable) (2018-04-09 r74565) -- "Unsuffered Consequences" Copyright (C) 2018 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) > library(survival) > data(cgd0) Warning message: In data(cgd0) : data set ?cgd0? not found ---- The data set is present and can be

I have a test directory for the survival suite, and dyn.load has ceased to work in it. Below shows the log: tmt1075% R --vanilla R version 2.12.2 (2011-02-25) Copyright (C) 2011 The R Foundation for Statistical Computing ISBN 3-900051-07-0 Platform: x86_64-unknown-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain

It is likely a problem with survival, since 2.9 merged in a large number of changes that had occured in my source tree that had not propogated to the R tree my test suite doesn't have a test for this particular case (2 factors) and - Murphy's law applies: although almost every possible case is covered in the test suite, any new error will hit an omitted combination of

Is there a way to include the compiled version of a vignette in the doc directory but mark it to NOT be rerun by CRAN??? I think I remember that this is possible, but have forgotton how.?? (It might even be a false memory.) Terry T. Background:? Beth Atkinson and I are splitting out many of the vignettes from the survival package into a separate package survivalVignettes.? There are a few

Since I read the list in digest form (and was out ill yesterday) I'm late to the discussion. There are 3 steps for predicting survival, using a Cox model: 1. Fit the data fit <- coxph(Surv(time, status) ~ age + ph.ecog, data=lung) The biggest question to answer here is what covariates you wish to base the prediction on. There is the usual tradeoff between too few (leave out something

I recently got a request to add head() and tail() methods for Surv objects, which is quite reasonable, but not unlike other requests for logLik,? vcov, extractAIC, ...?? What they all have in common is that are methods added since creation of the survival package, and that I didn't know they existed. To try and get ahead of the curve, is there a way to list names of all of the default

I am now getting the occasional complaint about survival routines that are not able to handle big data.?? I looked in the manuals to try and update my understanding of max vector size, max matrix, max data set, etc; but it is either not there or I missed it (the latter more likely).?? Is it still .Machine$integer.max for everything??? Will that change??? Found where? I am going to need to go

This question likely has a 1 line answer, I'm just not seeing it. (2, 3, or 10 lines is fine too.) For a vector I can do group <- match(x, unqiue(x)) to get a vector that labels each element of x. What is an equivalent if x is a data frame? The result does not have to be fast: the data set will have < 100 elements. Since this is inside the survival package, and that package is on