Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

masking ranef (from "nlme" or "lme4") #5

Closed
mmaechler opened this issue Mar 7, 2017 · 0 comments · Fixed by #6
Closed

masking ranef (from "nlme" or "lme4") #5

mmaechler opened this issue Mar 7, 2017 · 0 comments · Fixed by #6

Comments

@mmaechler
Copy link
Contributor

The metafor package provides an S3 method for ranef(). Because it "forgets" to import the S3 generic (from nlme or lme4), a new ranef() S3 generic is automatically created.

This leads to a warning in the following, but more importantly, ranef() will stop working for nlme or lme4 objects where it should work:

> require(nlme)
> require(metafor)
Loading required package: metafor
Loading 'metafor' package (version 1.9-9). For an overview 
and introduction to the package please type: help(metafor).

Attaching package:metaforThe following object is masked frompackage:lme4:

    ranef

AFTER fixing the problem (see pull request) the warning (" ... masked ... " ) disappears and more importantly, after loading the two packages, methods(ranef) does show both nlme and metafor methods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant