# Resources for using classify-consensus-blast on 16S data

**URL:** <https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504>\
**Category:** Silva\
**Tags:** feature-classifier, silva, greengenes, taxonomy\
**Created:** [June 25, 2020, 11:15pm UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504 "2020-06-25T23:15:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![emmzee](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/e/67e7ee/32.png) [@emmzee](https://forum.qiime2.org/u/emmzee)\
**Post date:** [June 25, 2020, 11:15pm UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504/1 "2020-06-25T23:15:34Z")

</div>

Hi everyone,

I've been researching the subject of assigning taxonomy -in terms of choice of database and method of classification- on Q2's forums and according to papers and official websites cited within. I am still not convinced to use sklearn, as I don't find it straightforward. Furthermore, compared to BLAST+, I find it more challenging to decide on specificities for sklearn - primarily due to inexperience using it. This is in spite of the good explanations of the confidence parameter and how to alter k-mer specifications for sklearn on the forums.

My question is, are there any resources available for SILVA or greengenes to use with BLAST consensus classifications on Q2 (i.e. separated reference sequences and associated taxonomy files)? I know there are pre-trained classifiers available for sklearn, but with such large databases, it is difficult to prepare reference database inputs for BLAST.

---

<div class="post-metadata">

**Author:** ![Nicholas\_Bokulich](https://forum.qiime2.org/user_avatar/forum.qiime2.org/nicholas_bokulich/32/19937_2.png) [@Nicholas\_Bokulich](https://forum.qiime2.org/u/Nicholas_Bokulich)\
**Post date:** [June 26, 2020, 5:37pm UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504/2 "2020-06-26T17:37:58Z")

</div>

> [@emmzee](#):
>
> I am still not convinced to use sklearn, as I don’t find it straightforward.

I hear your concern. Sometimes complexity is good, though. We designed and optimized the classify-sklearn method to work "out of the box" so that you can use the default settings and get reasonable results without the need for a user to adjust the settings or intimately understand how it works.

Still, I get it if you'd rather use something you have better control over. In that case I recommend using the `classify-consensus-vsearch` method, which is just much better than `classify-consensus-blast`, and has more features to give you _more control_.

See here for more description of all of these methods, and benchmarking results:

> **[Optimizing taxonomic classification of marker-gene amplicon sequences with...](https://microbiomejournal.biomedcentral.com/articles/10.1186/s40168-018-0470-z)**
>
> Background Taxonomic classification of marker-gene sequences is an important step in microbiome analysis. Results We present q2-feature-classifier ( https://github.com/qiime2/q2-feature-classifier ), a QIIME 2 plugin containing several novel...

> [@emmzee](#):
>
> My question is, are there any resources available for SILVA or greengenes to use with BLAST consensus classifications on Q2 (i.e. separated reference sequences and associated taxonomy files)?

Yes, on the same [data resources page](https://docs.qiime2.org/2020.2/data-resources/) where the pretrained classifiers are found.

But I recommend waiting until next week when the next release of QIIME 2 comes out, and then take a look at the [2020.6 release data resources](https://docs.qiime2.org/2020.6/data-resources/). The SILVA database files were built in a better way, using [RESCRIPt](https://forum.qiime2.org/t/processing-filtering-and-evaluating-reference-sequence-data-with-rescript/15494)

---

<div class="post-metadata">

**Author:** ![emmzee](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/e/67e7ee/32.png) [@emmzee](https://forum.qiime2.org/u/emmzee)\
**Post date:** [July 7, 2020, 5:09pm UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504/3 "2020-07-07T17:09:05Z")

</div>

Thanks for sharing that article and the resources, @Nicholas_Bokulich! I completed a comparison of my samples using vsearch and my own trained classifier, and didn't observe any major differences in community composition. In training a classifier, I extracted reference reads with the same parameters I used in DADA2. In my comparison, I kept the parameters for the extracted reference reads the same in terms of `--p-trunc-len` and `--p-trunc-left`. Is that OK? Does changing these parameters have any significant impact on the trained classifier?

---

<div class="post-metadata">

**Author:** ![Nicholas\_Bokulich](https://forum.qiime2.org/user_avatar/forum.qiime2.org/nicholas_bokulich/32/19937_2.png) [@Nicholas\_Bokulich](https://forum.qiime2.org/u/Nicholas_Bokulich)\
**Post date:** [July 7, 2020, 7:56pm UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504/4 "2020-07-07T19:56:16Z")

</div>

> [@emmzee](#):
>
> In my comparison, I kept the parameters for the extracted reference reads the same in terms of `--p-trunc-len` and `--p-trunc-left` . Is that OK?

Perfect

> [@emmzee](#):
>
> Does changing these parameters have any significant impact on the trained classifier?

It could... if the extracted read are shorter than the query, it's bad news (could lead to unclassified or misclassified reads). If longer, it doesn't make a big difference (e.g., if you extract to the primer regions but don't trim/truncate more)

---

<div class="post-metadata">

**Author:** ![system](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/3X/2/1/21af5fe23cb6f4579467c66a9ed94e55274ca7bd.svg) [@system](https://forum.qiime2.org/u/system)\
**Post date:** [August 8, 2020, 2:09am UTC](https://forum.qiime2.org/t/resources-for-using-classify-consensus-blast-on-16s-data/15504/5 "2020-08-08T02:09:49Z")

</div>

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
