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

Toptable: Error: $ operator not defined for this S4 class #63

Closed
dcpattie opened this issue Dec 13, 2018 · 1 comment
Closed

Toptable: Error: $ operator not defined for this S4 class #63

dcpattie opened this issue Dec 13, 2018 · 1 comment
Assignees
Labels

Comments

@dcpattie
Copy link

Below is another error I found executing the pipeline:

head(toptable(limmaTMLEout))
Error: $ operator not defined for this S4 class

@nhejazi nhejazi self-assigned this Dec 14, 2018
@nhejazi nhejazi added the bug label Dec 14, 2018
@nhejazi
Copy link
Owner

nhejazi commented Dec 17, 2018

I was able to reproduce this problem using v1.6.0 of biotmle from Bioconductor 3.8. Please note that this is happening because of a difference between the development version of biotmle and the version of the package available from the 3.8 release of Bioconductor. To clarify, this happens because v1.6.0 of biotmle does not include the accessor function toptable (here in the development version v1.7.2 of biotmle on GitHub master) --- as such, the call to toptable above is actually calling the wrong function, namely limma::toptable (and not biotmle::toptable).

To use the native toptable accessor function from biotmle, consider installing v1.7.2 of the packages from GitHub via

remotes::install_github("nhejazi/biotmle@master")

Alternatively, note that the toptable accessor function is a convenience, and the same output may be extracted by a call that explicitly uses @ to access the appropriate slot. Thus, to extract the same information from your currently installed version of biotmle, please consider using

head(limmaTMLEout@topTable)

Please feel free to re-open this issue if this does not resolve your current problem. Hope this helps.

@nhejazi nhejazi closed this as completed Dec 17, 2018
@nhejazi nhejazi mentioned this issue Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants