-
Notifications
You must be signed in to change notification settings - Fork 19
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
AttributeError: 'Predictor' object has no attribute '__set_up_prodigal_thread' #21
Comments
Having the same errors with my bins and the |
Same here! @chklovski |
Me too, did anyone figure it out? |
@emma-bell I never figured it out. Ended up just going with the original CheckM. The CheckM2 documentation suggested for the organisms I was working with (Gammaproteobacteria), CheckM and CheckM2 would provide fairly similar results. Would love to get it working for future projects though, so if anyone is able to fix this issue, please drop the info on how you resolved the issue on this thread! |
Apologies for the late reply. If you want to try checkm2 again, please install it via bioconda and let me know if the issue persists. |
Thank you @chklovski and @kellikmullane, checkm2 now works for me with the latest release (conda install) :) |
Hey - thanks for this tool! Really excited to start using it. I used the "Run without Installing" method to use CheckM2 and I keep getting the error:
AttributeError: 'Predictor' object has no attribute '__set_up_prodigal_thread'
I get this with both bin/checkm2 testrun and CheckM2 predict with my own genomes. I thought it was a python version compatibility issue so I tried installing the version listed in the .yml file. I also tried actually installing it. In both cases, I either get this exact same error, or something very similar like:
AttributeError: module 'main' has no attribute 'spec' or
AttributeError: 'Predictor' object has no attribute '__reportProgress'
Any clues as to what could be going on? Not sure if it's an issue on my end or what. Appreciate any advice/help you can give!
The text was updated successfully, but these errors were encountered: