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

Human reads are actually outputted by nohuman #2

Closed
cpauvert opened this issue Jul 21, 2024 · 3 comments
Closed

Human reads are actually outputted by nohuman #2

cpauvert opened this issue Jul 21, 2024 · 3 comments

Comments

@cpauvert
Copy link

Hi @mbhall88,
thanks for developing this tool, this approach is indeed very fast!
However when trying out on bacterial genome assembly data (Nanopore and Illumina) I was puzzled that nohuman was throwing the baby out with the bathwater. Therefore I investigated with the manual approach described in https://github.com/mbhall88/classification_benchmark with kraken2 and got:

277081 sequences (1116.92 Mbp) processed in 16.112s (1031.8 Kseq/m, 4159.33 Mbp/m).
  2814 sequences classified (1.02%).
  274267 sequences unclassified (98.98%)   

But the output file from nohuman contained 2814 sequences, which I trace the typo to be:

kraken_cmd.extend(&["--classified-out", &outfile]);

I submitted a PR to fix that unclassified reads are wanted, but I'm not familiar with Rust, so I could not recompile/test properly, let me know if I can try out something.

Best,
Charlie

@mbhall88
Copy link
Owner

Oh wow! This is embarrasing!! Amazing how two characters can make this a completely different program. Thank you so much for detecting this. It will be fixed in v0.1.1

@cpauvert
Copy link
Author

You're welcome @mbhall88! Typos happened and having the code available helps so much in these situations! Thanks for the quick reaction!

@mbhall88
Copy link
Owner

bioconda package should now be updated btw

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

Successfully merging a pull request may close this issue.

2 participants