# Issues with Classifiers in QIIME 2 - Unusual Assignments Over 99% **URL:** \ **Category:** User Support\ **Tags:** taxonomy\ **Created:** [September 18, 2024, 9:08pm UTC](https://forum.qiime2.org/t/issues-with-classifiers-in-qiime-2-unusual-assignments-over-99/31450 "2024-09-18T21:08:17Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![SoilRotifer](https://forum.qiime2.org/user_avatar/forum.qiime2.org/soilrotifer/32/21071_2.png) [@SoilRotifer](https://forum.qiime2.org/u/SoilRotifer)\ **Post date:** [September 25, 2024, 1:36pm UTC](https://forum.qiime2.org/t/issues-with-classifiers-in-qiime-2-unusual-assignments-over-99/31450/16 "2024-09-25T13:36:24Z")
Hi @JvWyatt, First, I'd like to say that I'm so sorry for your loss! I certainly know what that's like. 😢 Secondly, these are very promising results! I would suggest altering the `--p-min-fold-parent-over-abundance` flag of DADA2, and set to `8` or `16`, as outline [here](https://forum.qiime2.org/t/trimming-output-problem/29631/14). This should help increase the non-chimeric values, as those are still quite low. A typical run often sees 70 - 80% chimeric reads. But they do get to ~ 50-60% on poor runs. Also, I think you'd be able to increase your merges if you set the following, as I mentioned earlier: ```auto --p-trunc-len-f 149 --p-trunc-len-r 149 ``` That last base for each read is quite high and could affect your merges. I'd also perform a simple sanity-check by running `dada2 denoise-single`. That is, only use the forward reads. This will give an upper-bound on the amount of data you can keep as you will not be dependent on merging. I've had to concede defeat for a few projects myself, where I only used the forward reads. This is totally fine. I do not think there is a need to re-orient your sequences, given how many appear to have successfully been classified. --- _[View the full topic](https://forum.qiime2.org/t/issues-with-classifiers-in-qiime-2-unusual-assignments-over-99/31450)._