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

Is directly using DIAMOND to assign taxonomy for reads not recommended? #138

Open
HuoJnx opened this issue Jan 7, 2025 · 0 comments
Open

Comments

@HuoJnx
Copy link

HuoJnx commented Jan 7, 2025

Hello team,

Thank you for providing the RAT tool. It has saved me a lot of time by efficiently combining information from MAGs and contigs to annotated taxonomy for reads.

I noticed that the file named *.complete.abundance.txt marks the "unmapped" reads as a single lineage labeled "unmapped," without providing further details.

If I want to retrieve the detailed lineage for the unmapped reads, it seems I need to parse the *.read2classification.txt file myself.

May I ask about the rationale behind this design choice? Is annotating taxonomy for reads directly with DIAMOND not recommended, or is there another reason?

image
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

1 participant