-
Notifications
You must be signed in to change notification settings - Fork 116
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
monocle2 result is not reproducible! #516
Comments
Hey! |
Hey :) thank you for your comment. I did what you mentioned: I placed "set.seed" at almost all step of the monocle2 pipeline, but it didn't work. And yes I did have saved data to .RDS files. However, the purpose of saving RDS file might be more on the "saving processing time" than "reproducibility". To whoever might come up with this issue, here is my workaround: downgrading R packages. I install 3.6 and install monocle 2.12.0. With this version, a single "set.seed" at the beginning of the script maintain the reproducibility of all results. :) |
I mean the purpose of saving data is to save the downsampled cells (corresponding barcodes actually) so that you can use thee same batch of cells to do downstream workflow, if you had done downsampling. If not, forget this job :) . BTW, your work is brilliant! |
Hello,
thank you for the great package. I'm curently using monocle 2.32.0 installed from bioconductor. During my analysis, I have observed that the DDRTree dimensional reduction, pseudotime assignment are not reproducible. With the same script and the same input (I'm also using docker to maintain all other packages, make sure they all have the same version and nothing out of control due to automatic update), I have got different result for each runs. Since the DDRTree dimensional reduction and the pseudotime were different, subsequent results were also different. I did set
set.seed(42)
at the beginning of the Rscript and any function I suspect it would affect, but the problem persists...I'm looking forward to hearing from you.
Best regards
HN
The text was updated successfully, but these errors were encountered: