Displaying 20 results from an estimated 4000 matches similar to: "importing S4 methods using a namespace"
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
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
2008 Apr 28
1
variable names when using S3 methods
I'm seeing some funny behavior when using methods (the older S3 type)
and having variables that start with the same letter. I have a vague
recollection of reading something about this once but now can't seem
to find anything in the documentation. Any explanation, or a link to
the proper documentation, if it does exist, would be appreciated.
Thanks, Aaron Rendahl
University of
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")
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
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
2003 Sep 05
1
namespaces and S4 methods/classes
The current version of the methods package now has a namespace. Packages
using S4 methods and classes can have NAMESPACE files. New directives
can be included in NAMESPACE files to import and export classes and
methods.
Namespaces allow cleaner definition of the API for packages, and are
needed for future improvements to R.
NOTE: This is a major revision. In principle, it should be back
2011 Oct 06
1
multiple defines of diag
The current coxme code has functions that depend on bdsmatrix and others
that depend on Matrix, both those pacakges define S4 methods for diag.
When loaded, the message appears:
replacing previous import ?diag? when loading ?Matrix?
Questions:
1. Do I need to worry about this? If so, what can I do about it?
I suppose I could add an importFrom directive, but it will be a pain
unless there
2006 Nov 01
56
ZFS/iSCSI target integration
Rick McNeal and I have been working on building support for sharing ZVOLs
as iSCSI targets directly into ZFS. Below is the proposal I''ll be
submitting to PSARC. Comments and suggestions are welcome.
Adam
---8<---
iSCSI/ZFS Integration
A. Overview
The goal of this project is to couple ZFS with the iSCSI target in Solaris
specifically to make it as easy to create and export ZVOLs
2007 Jan 15
4
iSCSI on a single interface?
Hi, are there currently any plans to make an iSCSI target created by
setting shareiscsi=on on a zvol
bindable to a single interface (setting tpgt or acls)?
I can cobble something together with ipfilter,
but that doesn''t give me enough granularity to say something like:
''host a can see target 1, host c can see targets 2-9'', etc.
Also, am I right in thinking without
2011 Dec 24
1
Call for Abstracts for useR! 2012
The international R User Conference useR! 2012 will be held June 12-15
at Vanderbilt University in Nashville, Tennessee, USA, with a
pre-conference full-day course offered on June 11.
Participants are encouraged to submit a one-page abstract for oral
or poster presentation at the conference. Half-day tutorials will be
held in the morning and afternoon of June 12th. For tutorials, please
2009 Jul 20
1
R package creation: 'show' extension not imported correctly
Dear List,
I have a problem related to R package creation.
I extended the 'show' method to cover a new class
with the following lines in the zzz.R file in the R directory while creating
an R package.
>setClass("rpa", contains="list")
>show.rpa <- function (...) {cat("rpa object \n")}
The corresponding lines were also added to NAMESPACE file:
2010 May 04
8
iscsitgtd failed request to share on zpool import after upgrade from b104 to b134
Hi,
I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving.
I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol''s ''vol01/zvol01'' and ''vol01/zvol02''.
During zpool import I am getting a non-zero exit code,
2009 Oct 23
1
inspect s4 methods
Hi everyone,
I'm sure this has been asked before, but I could not find the right
search terms to find it.
If I want to see what summarizing a model fit with lm() does, I can
write "summary.lm". But what if I want to see what summarizing a model
fit with lmer() (lme4 package) does?
showMethods(summary)
Function: summary (package base)
object="ANY"
2007 Jan 14
3
changes in the structure of mer objects?
Dear all,
I try to run the example of lmer and get the following error message.
> library(lme4)
> example(lmer)
lmer> (fm1 <- lmer(Reaction ~ Days + (Days | Subject), sleepstudy))
[[1]]
Error in get(x, envir, mode, inherits) : variable "as.dpoMatrix" was not
found
This error message is similar to what I get with other models. It looks
like the mer class has a slightly
2009 Oct 19
1
Defining S3-methods for S4-objects: cannot coerce type 'S4' to vector of type 'integer'
In the 'doBy' package there is an esticon() function for calculating linear contrasts for various model types. I have defined an S3-method 'esticon.mer()' for 'mer' objects from the lme4 package. Building the package and invoking the method gives:
> esticon(fm1, c(1,1))
Confidence interval ( WALD ) level = 0.95
Error in as.integer(x) :
cannot coerce type 'S4'
2007 Jun 25
1
conflict between lme4 and RMySQL packages (PR#9753)
Full_Name: Dale Barr
Version: 2.5.1 (patched)
OS: Ubuntu linux x86_64
Submission from: (NULL) (138.23.70.108)
When RMySQL is loaded in before lme4, the summary() function for lmer objects in
the lme4 packages produces the following error:
Error in printMer(object) : no slot of name "status" for this object of class
"table"
When RMySQL is loaded AFTER lme4, however, no such
2008 Aug 20
3
bug in lme4?
Dear all,
I found a problem with 'lme4'. Basically, once you load the package 'aod' (Analysis of Overdispersed Data), the functions 'lmer' and 'glmer' don't work anymore:
library(lme4)
(fm1 <- lmer(Reaction ~ Days + (Days|Subject), sleepstudy))
(gm1 <- glmer(cbind(incidence, size - incidence) ~ period + (1 | herd),
family = binomial, data
2010 Nov 01
3
Mean and individual growth curve trajectories
I'm trying to understand how to plot individual growth curve trajectories,
with the overall mean trajectory superimposed (preferably in a slightly
thicker line, maybe in black) over the individual trajectories. Using the
sleepstudy data in lme4, here is the code I have so far:
library(lme4)
library(lattice)
xyplot(Reaction ~ Days, data = sleepstudy, group = Subject, type = 'l')