-
Notifications
You must be signed in to change notification settings - Fork 11
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
Not reproducible results #48
Comments
Coming into this a bit late, but there is a random seed setting as one of the parameters and sampling is mentioned in the documentation, so I think this is both completely expected and possible to make reproducible by setting
|
Dear @cjfields, Could you clarify how you use the I tried to run version Here are the commands I executed: nonpareil -s some.reads.fq -T kmer -f fastq -r 23 -b test.1
nonpareil -s some.reads.fq -T kmer -f fastq -r 23 -b test.2 |
Thanks for bringing this up to our attention! I have now implemented consistency with For @gunturus Do you think the kmer kernel could be migrated to a deterministic implementation instead? |
Happy to see @lmrodriguezr 's answer (and agree that it's good you raised it); I planned on replying that this sounds like a definite bug. |
Dear @lmrodriguezr and @cjfields, Thank you both for looking into this! |
Hello,
I have a question regarding the reproducibility of the results: I ran
nonpareil
on the same input using the same command line and got slightly different results for both runs.Is that something to be expected? Do you know what the source of this randomness is and whether the analysis could be made deterministic in the future?
Used version:
nonpareil=3.3.3=r341h470a237_0
installed viaconda
Thank you in advance!
Best,
Valentina
The text was updated successfully, but these errors were encountered: