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

save R objects as RDS #610

Closed
ChristopherBarrington opened this issue Apr 26, 2021 · 1 comment
Closed

save R objects as RDS #610

ChristopherBarrington opened this issue Apr 26, 2021 · 1 comment

Comments

@ChristopherBarrington
Copy link

In the results directory, there are RData files, provided from the DESeq2 script. The objects are loaded into a workspace with load so will overwrite any existing similarly named variable and requires the user to know what the variable(s) in the DESeq script were called.

It may be more user-friendly to use an RDS object instead so that it can be read into any variable, independently of its original name in the DESeq script. As far as I can see, this would only apply to the two files/objects below, though I haven't used any quantification methods than rsem.

results/star_rsem/deseq2_qc/deseq2.dds.RData
results/star_rsem/deseq2_qc/size_factors/deseq2.size_factors.RData
@drpatelh
Copy link
Member

Ping @macroscian . If you guys fancy coming up with a fix in the next couple of days it will be in the next release.

drpatelh added a commit that referenced this issue Apr 28, 2021
Fix #610 Save DESeq2 objects as both rds and rdata
drpatelh added a commit that referenced this issue May 5, 2021
Update output docs regarding #610
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants