# Results different after training feature classifier

**URL:** https://forum.qiime2.org/t/results-different-after-training-feature-classifier/21641
**Category:** Technical Support
**Created:** [December 13, 2021, 7:09am UTC](https://forum.qiime2.org/t/results-different-after-training-feature-classifier/21641 "2021-12-13T07:09:27Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![kamalghazali](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/k/ce73a5/32.png) [@kamalghazali](https://forum.qiime2.org/u/kamalghazali)
#### Post date: [December 13, 2021, 7:09am UTC](https://forum.qiime2.org/t/results-different-after-training-feature-classifier/21641/1 "2021-12-13T07:09:27Z")

</div>

Hello everyone!

We ran the analysis against the UNITE ITS database, however the result included the genus Ciliophora, which was unexpected. Despite the fact that the genus Ciliophora exists in the kingdom Fungi, all of the sequences classified as Ciliophora must be considered Alveolata sequences (Kingdom Protista) and we would like to remove them from our analysis.

We removed the Ciliophora genus from both files (just one that matched to the genus) and reran the classifier training as follows, using the taxonomy and fasta sequence from the UNITE ITS database.

> qiime tools import   
> --type 'FeatureData[Sequence]'   
> --input-path unite\_sh\_refs\_qiime\_ver8\_97.fasta   
> --output-path unite\_sh\_refs\_qiime\_ver8\_97.fasta.qza

> qiime tools import   
> --type 'FeatureData[Taxonomy]' [Uploading  
> --input-format HeaderlessTSVTaxonomyFormat   
> --input-path unite\_taxonomy\_qiime\_ver8\_97.txt   
> --output-path unite\_taxonomy\_qiime\_ver8\_97.txt.qza

> qiime feature-classifier fit-classifier-naive-bayes   
> --i-reference-reads unite\_sh\_refs\_qiime\_ver8\_97.fasta.qza   
> --i-reference-taxonomy unite\_taxonomy\_qiime\_ver8\_97.txt.qza   
> --o-classifier unite-its-97-classifier.qza

However, when compared to the previous version, the new runs turn out to be somewhat different. When comparing the ASV tables from the two runs, I noticed that a few ASVs that were previously matched to another taxonomy were no longer matched to groups in the new run. Example output between the 2 experiment is shown here (phylum barchart

 ![Test_run1-vs Test_run2](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/2X/b/bba258fb777cbf4e25eef06d999be6eacb4b2229.png) ) . Any reason why the results are very different just by removing 1 sequence?

Thanks in advance

Kamal

---

<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: [December 13, 2021, 7:51am UTC](https://forum.qiime2.org/t/results-different-after-training-feature-classifier/21641/2 "2021-12-13T07:51:58Z")

</div>

Hi @kamalghazali welcome to the forum!

It sounds like your reads are in mixed orientations. See this topic for more details on what is happening, and some troubleshooting steps:

> [@Bug when classifying isolate 16S sequences](https://forum.qiime2.org/t/bug-when-classifying-isolate-16s-sequences/11984/2):
>
> Hi @laurenmlui, Very strange. To give me something to work with, would you mind running qiime metadata tabulate on the full data (~1000 seqs) and non-buggy test subset (7-10 seqs) and posting the QZVs here? Are your reads all in the same orientation? What happens with you add --p-read-orientation same (or --p-read-orientation reverse-complement) to the command? I suspect the orientation predictor is going haywire so setting the correct orientation may set things straight. Why do I think that…

---

<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: [January 13, 2022, 1:52pm UTC](https://forum.qiime2.org/t/results-different-after-training-feature-classifier/21641/3 "2022-01-13T13:52:23Z")

</div>

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