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

whether Taxonomy barplot made in R from squeezemeta output represents taxonomy of reads or assembly #923

Closed
mohitsharma-123 opened this issue Jan 20, 2025 · 3 comments

Comments

@mohitsharma-123
Copy link

Hello
I want to know that i have ran squeezemeta on my 4 samples using metaspades and coassembly mode.
I m using R workflow provided in this program for analyzing my squeezemeta output.
I want to know whether the taxonomy plots generated will represent taxonomy at reads level or of assembly.
Also when i m using tools like kaiju, centrifuger on both reads from fastp and metaspades assembly i found huge difference in taxonomy and read taxonomy is aligning more with squeezemeta output

plotTaxonomy(Hadza, rank='phylum', count='percent')

@jtamames
Copy link
Owner

Hello
If you did co-assembly, the all the information refers to the coassembly. You won´t have any classification of reads unless you use sqm_reads.pl or sqm_longreads.pl
It is not rare to have differences between these other tools and squeezemeta since they use different methods for the annotation. Check our paper on this subject if https://doi.org/10.1186/s12864-019-6289-6

Best,
J

@mohitsharma-123
Copy link
Author

So, for metaspades assembly taxonomy which one is more preferable Squeezemeta, kaiju, kraken2, centrifuger
also for reads level which one you suggest.
Thank you very much for your reply really appreciate your response.
Thanks for wonderful program.

@jtamames
Copy link
Owner

SqueezeMeta, obviously! lol

@fpusan fpusan closed this as completed Feb 18, 2025
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

No branches or pull requests

3 participants