similar to: multiple defines of diag

Displaying 20 results from an estimated 1000 matches similar to: "multiple defines of diag"

2018 Jan 09
1
resolving a names conflict
The survival package uses a generalized cholesky decompostition throughout.? If A is a symmetric matrix A= LDL' where L is lower triangular with 1s on the diagonal, D is diagonal, and D[i,i] =0 if column i of A is redundant.? Being able to read the rank and dependencies directly off of D is very handy. The bdsmatrix package uses the same, but exposes it to the user as gchol and solve
2015 Feb 15
2
Imports problem
I'm testing out a new version of coxme and R CMD check fails with "could not find function ranef" (or random.effects or fixef, or anything from nlme). The NAMESPACE file has the line below importFrom(nlme, ranef, random.effects, fixef, fixed.effects, VarCorr) and nlme is declared in the DESCRIPTION file as an import. I feel that I must be staring at some obvious (but
2015 Mar 02
5
Import data set from another package?
I've moved nlme from Depends to Imports in my coxme package. However, a few of the examples for lmekin use one of the data sets from nlme. This is on purpose, to show how the results are the same and how they differ. If I use data(nlme::ergoStool) the data is not found, data(nlme:::ergoStool) does no better. If I add importFrom(nlme, "ergoStool") the error message is that
2007 May 03
1
Imports/exports of S4 methods
I have a question about what to do in the following situation (please bear with the setup): Package A defines an S4 generic 'foo' and as well as S4 methods for 'foo' and has exportMethods("foo") in its NAMESPACE file. Package B defines another method for 'foo' for class "bar" and has importFrom(A, "foo") exportMethods("foo")
2009 Aug 13
2
CMD check error (bug?)
R version 2.9.0 running on Centos (Red Hat linux). I have a pair of packages coxme and bdsmatrix. The latter is installed in my local library (I don't have permission for global install at work.) That is, it is in the location pointed to in R_LIBS_USER. In R, the command library(bdsmatrix) works fine. Coxme depends on bdsmatrix, in fact uses some cross-calls to it's C routines, which
2005 Nov 28
1
import of Namespaces
Dear R devels, let's say I have three packages "pkg1", "pkg2" and "pkg3" which all contain new S4 classes and methods. Where "pkg3" depends on "pkg2" and "pkg2" depends on "pkg1". Moreover, all three packages have namespaces. 1) I use ".onLoad <- function(lib, pkg) require(methods)". Do I also have to
2017 Dec 29
3
winbuilder warning message wrt function pointers
I've recently updated the coxme package, which calls internal routines from the bdsmatrix package.? (It is in fact mentioned as an example of this in the Extensions manual.) The call connections are a blocks like this, one for each of the 9 called C routines. void bdsmatrix_prod4(int nrow,??? int nblock,?? int *bsize, ??????????????????? double *bmat, double *rmat, ??????????????????? int
2008 Mar 05
1
coxme - fitting random treatment effect nested within centre
Dear all, I am using "coxme" function in Kinship library to fit random treatment effect nested within centre. I got 3 treatments (0,1,2) and 3 centres. I used following commands, but got an error. > ugroup=paste(rep(1:3,each=3),rep(0:2,3),sep='/') > mat1=bdsmatrix(rep(c(1,1,1,1,1,1,1,1,1),3),blocksize=rep(3,3),dimnames=list(ugroup,ugroup)) >
2009 Mar 05
3
methods package
I'm working on the next version of coxme, one step of which is converting the bdsmatrix library from Splus to R. Actually, it is a conversion from S4 methods as first described in the Green book to S4 methods as they currently exist. Mostly it's going ok, but not entirely. 1. The biggest issue is lack of documentation. The online help pages have not been a help; they keep saying
2017 Dec 29
1
winbuilder warning message wrt function pointers
And remove the cast on the return value of R_GETCCallable. And check that your function is found before using it. #include <R.h> #include <Rinternals.h> #include <R_ext/Rdynload.h> void bdsmatrix_prod4(int nrow, int nblock, int *bsize, double *bmat, double *rmat, int nfrail, double *y) { DL_FUNC fun = NULL; if (fun==NULL)
2011 Mar 26
1
another import puzzle
Dear list, I have another (again possibly boneheaded) puzzle about importing, again encapsulated in a nearly trivial package. (The package is posted at <http://www.math.mcmaster.ca/bolker/misc/coefsumtest_0.001.tar.gz>.) The package consists (only) of the following S3 method definitions: coeftab <- function(object, ...) UseMethod("coeftab",object) coeftab.default <-
2008 Apr 02
2
restrictions for attribute access <Watchdog: Virus checked>
Hello everybody, I have a problem with accessing class attributes. I think it might be due to namespace access restrictions or something similar, but I'm unable to figure it out, maybe someone knows the trick how to do it ... I'm trying to extract some information from the summary object for a model fitted using the lmer function from the lme4 package: smry <- summary(lmer(foo
2009 Aug 05
1
inheriting C symbols
The package coxme depends heavily on bdsmatrix, to the point of needing access to some of its C calls. The kinship package (in progress) uses the R level functions in bdsmatrix, but not the C calls. That is, I don't want to always export the symbols. For testing I can use an explicit dyn.load('somepath/bsdmatrix.so', local=F). How do I incorporate such a dependency in the
2012 Sep 06
1
How to extract p value from the lmekin object obtained by fitting mixed model with function lmekin() in package coxme?
Hi, R experts I am currently using lmekin() function in coxme package to fit a mixed effect model for family based genetic data. How can I extract the p value from a lmekin object? When I print the object in R console, I can see the p value and Z value are just over there. But I can not extract them by the coef() function. kinfit$coefficient$fixed (kinfit is the name of the lmekin object)
2010 Mar 05
2
Defining a method in two packages
The coxme package has a ranef() method, as does lme4. I'm having trouble getting them to play together, as shown below. (The particular model in the example isn't defensible, but uses a standard data set.) The problem is that most of the time only one of lme4 or coxme will be loaded, so each needs to define the basic ranef function as well as a method for it. But when loaded together
2015 Feb 16
0
Imports problem
>>>>> Therneau, Terry M , Ph D <therneau at mayo.edu> >>>>> on Sun, 15 Feb 2015 17:31:00 -0600 writes: > I'm testing out a new version of coxme and R CMD check fails with "could not find function > ranef" (or random.effects or fixef, or anything from nlme). The NAMESPACE file has the > line below >
2009 Mar 05
3
Package issue
I've converted the bdsmatrix package (used by coxme) to the newer style of S4, and uploaded it. It is in the pkg directory of survival, on r-forge. I'm stuck on something that is almost certainly a namespace issue. I've borrowed liberally from Matrix (a big help) and read the documentation, and just upgraded to 2.8.1 - but still stuck. All the tests work when I run them "by
2010 Apr 23
2
Deferred Default Marker
I've finally narrowed down a puzzling problem: here is the short test case. tmt34% R --vanilla R version 2.10.0 (2009-10-26) Copyright (C) 2009 The R Foundation for Statistical Computing ISBN 3-900051-07-0 > temp <- matrix(runif(50), ncol=2) > t(temp) %*% temp [,1] [,2] [1,] 7.916016 6.049698 [2,] 6.049698 7.650694 > library(kinship) Loading required package:
2004 Jan 08
3
S3, S4, namespace
I have encountered an issue which I have been unable to resolve, involving an S3 generic (print) being declared S4 generic in a package, and the method being exported. This all works fine - the problem occurs when I try to import the method to another package. Here is the bit that works fine. ------------- #the .r file for package bar
2011 Dec 15
1
S4 NAMESPACE method imports and exports do not include (promoted?) generics
In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" section 1.6.6 of 'Writing R Extensions' says Note that exporting methods on a generic in the namespace will also export the generic, and exporting a generic in the namespace will also export its methods. and Note that importMethodsFrom will also import any generics defined in