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

moving data content to sysdata? #74

Open
pawelqs opened this issue Jul 8, 2022 · 0 comments
Open

moving data content to sysdata? #74

pawelqs opened this issue Jul 8, 2022 · 0 comments

Comments

@pawelqs
Copy link

pawelqs commented Jul 8, 2022

Hi!

It is hard to run deconstructSigs as a part of a custom package, since Rda files from data dir are not loaded when deconstructSigs is added to the Imports section (tri.counts.genome object is not available). Since it is not an example data, but an object required by package for proper working, could you consider moving it to R/sysdata.rda?

Thread that describes the problem, which helped to me temporarily solve it by adding deconstructSigs to Dependencies, which is a bad practice -> https://stackoverflow.com/questions/22389993/r-package-namespace-issue-using-data-data-set-not-found
R packages on sysdata -> https://r-pkgs.org/data.html#data-sysdata

Thanks for great software! ;)

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

No branches or pull requests

1 participant