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

pop from empty list error when taxonomy label not complete #93

Open
BenKaehler opened this issue Oct 18, 2017 · 12 comments
Open

pop from empty list error when taxonomy label not complete #93

BenKaehler opened this issue Oct 18, 2017 · 12 comments
Labels
bug-sev:2|low type:bug Something is wrong.

Comments

@BenKaehler
Copy link
Member

BenKaehler commented Oct 18, 2017

Bug Description
If one of the taxonomies is not complete, for instance

k_Eukaryota; p_Parabasalia; c_Hypotrichomonadea; o_Hypotrichomonadida; f_Hypotrichomonadidae; g_Trichomitus sp.

does not go all the way to species level, you get an uninformative pop from empty list error when you run classify-sklearn.

Comments
It would be better if there was an error message when training the classifier.

References
This issue was discovered here.

@jairideout jairideout added the type:bug Something is wrong. label Oct 19, 2017
@ssavvi
Copy link

ssavvi commented Jan 8, 2021

I am also getting this error. Is there anyway to resolve this . Issue occurs with QIIME2 version 2019.10 onwards .

@ssavvi
Copy link

ssavvi commented Jan 9, 2021

Just ran feature classifier classif- sklearn with silva-138-99-515-806-nb-classifier version and this bug was no longer an issue ! Thanks

@XrandallX
Copy link

Hello,

I also received the original message and I tried to correct by the following addition to the code based on the following thread

https://forum.qiime2.org/t/plugin-error-from-feature-classifier-pop-from-empty-list/1431/11

qiime feature-classifier classify-sklearn --i-reads rep-seqs.qza --i-classifier classifier.qza --o-classification result.qza --p-confidence -1 --p-read-orientation same

This is the new error I received regarding the --p- confidence -1 section below

Would anyone have any ideas on how to deal with this please?

Thank you.

Plugin error from feature-classifier:

Parameter 'confidence' received -1 as an argument, which is incompatible with parameter type: Float % Range(0, 1, inclusive_end=True) | Str % Choices('disable')

Debug info has been saved to /tmp/qiime2-q2cli-err-dc8df57b.log

@nbokulich
Copy link
Member

Hi @XrandallX ,

Please open a topic on the forum for troubleshooting issues — you are receiving a different error message that is not related to this issue.

@ncep112
Copy link

ncep112 commented Mar 15, 2022

Hello,

I also got this error when I used QIIME 2 version 2022.2. I made a classifier file (silva-138-ssu-nr99-515f-806r-classifier.qza) following the steps in the RESCRIPt tutorial. Using the qiime rescript dereplicate command, I made a consensus classifier file using the -lca option. I thought this command was supposed to fill the lower-level taxonomy with empty place-holders to prevent this issue from happening, so I am not sure what is causing the error. Do you have any advice?

Thank you for your help; it is greatly appreciated!

@ssavvi
Copy link

ssavvi commented Mar 15, 2022 via email

@ncep112
Copy link

ncep112 commented Mar 15, 2022

@ssavvi thanks for the response! I was creating and training my own classifier file instead of using a pre-made one and received this error when I tried to assign taxonomy to my req-seqs.qza file. Did you use a pre-made classifier or create your own?

@ssavvi
Copy link

ssavvi commented Mar 15, 2022 via email

@nbokulich
Copy link
Member

Hi @ncep112 and @ssavvi please post all user support questions to the QIIME 2 forum, thank you.

@nbokulich nbokulich reopened this Mar 16, 2022
@gregcaporaso
Copy link
Member

@nbokulich, do you know if this is a bug that needs to be addressed (e.g., with a better error message)?

@nbokulich
Copy link
Member

yes this still has not been addressed, please leave open.

@Thainacortezs
Copy link

Thainacortezs commented Dec 5, 2023

I had the same issue and what I did was to use a python script to fix the taxon file to adjust the pattern of taxonomic identifications, where all the sequences had the exactly same hierarchical levels. Even if the level wasn't there for some sequences, I just classified as 'unknown'. That way all the sequences had the same amount of classifications. Hope it helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-sev:2|low type:bug Something is wrong.
Projects
None yet
Development

No branches or pull requests

8 participants