-
Notifications
You must be signed in to change notification settings - Fork 141
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
Wrong classification results for some ASVs (assignTaxonomy function) #1441
Comments
I ran the following:
So I can reproduce what you are observing. Then added the subsequent check for reverse complement orientation:
So, it looks like the first misclassification is because the first query sequence is in the reverse complement orientation to the reference database. It's probably best off to always use The second I think simply reflects a shortcoming of the naive Bayesian classifier method (which is what |
Hi Benjamin, The reference database I'm using is a subset of the 16S sequences extracted from whole genomes by the GTDB, so I'm confused as to how it can contain reverse complemented sequences. But I'm glad that there is such a simple fix to the problem! Thank you so much for your help! Best wishes, |
Hi @benjjneb and fellow DADA2 fans,
I noticed recently that for a very small number of ASVs, the DADA2
assignTaxonomy
function is returning a classification that is obviously wrong.I'll give two examples. In the first, an ASV is classified to the genus Lentilactobacillus by DADA2, while a BLASTN search against the exact same reference database results in a perfect match with a Lactiplantibacillus 16S sequence. In the second example, an ASV is classified to the species Apilactobacillus apinorum, while the best BLASTN hit against the same reference database is to the genus Lacticaseibacillus (with only 92% identity, which makes sense because according to EzBioCloud, the ASV is a Weissella, which isn't present in the reference database).
Here is the code for the examples. Any help is greatly appreciated.
Cheers,
Stijn
The text was updated successfully, but these errors were encountered: