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

FAQ: SPAdes, and thus Jovian, is only comparable across systems/installations if the same amount of threads are used for assembly. #145

Open
DennisSchmitz opened this issue May 18, 2020 · 0 comments
Assignees
Labels
faq Frequently asked question wontfix This will not be worked on

Comments

@DennisSchmitz
Copy link
Owner

TLDR The Jovian output is only comparable between systems/installations with 12 or more computing threads.

After running a demo dataset, with known outputs/hashes, on a system with limited resources (<12 computing threads) the hashes of the output files didn't match the expected values. I traced this back to the SPAdes output. After some digging, I found that SPAdes output differs based on the number of threads that are used. On this system, snakemake lowered the number of threads (default=12) for the de novo assembly rule to abide the available resources, thus generating different output, and deviant hashes.

I'll keep this issue open as a reminder to avoid future confusion and hopefully this saves someone some time.

@DennisSchmitz DennisSchmitz added wontfix This will not be worked on faq Frequently asked question labels May 18, 2020
@DennisSchmitz DennisSchmitz self-assigned this May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
faq Frequently asked question wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant