-
Notifications
You must be signed in to change notification settings - Fork 8
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
Internal KeyError when processing externally generated gene calls #12
Comments
Think I figured it out. It looks like the basename extracted from the diamond output file will include the original extension, while the gene counts are stored in the filename without the extension. Running GUNC using gene calls without an extension (e.g. |
Yeah i just saw that too.. i can only apologise for that. I will release a new version with a fix as soon as i can, at least for now you could run without an extension. Thanks for pointing it out though.. i dont know how that got through testing.. |
No worries, happens to all of us. |
I just released v1.0.3 which should fix this issue.. it is taking a while to appear on conda but once its there this issue should be solved! if you notice any other issues do let me know.. thanks again. |
Hi @fullama, As far as I have understood, there are two possibilities of fix: The A solution could be complemented by a last read of the json, trimming of the suffixes and rewrite, for compatibility purpose. |
hi, im not sure i understand whats happening here.. did you run with |
My bad, it worked with |
Hi,
I am using gunc v1.0.2 in a fresh Conda environment to perform chimerism checks on a few test genomes. I have already generated Prodigal calls, so I am providing them as the input fasta after setting the gene_calls flag.
Initial command:
After DIAMOND finishes running, I consistently get the following error:
Since the basename is generated by this line of code:
basename = os.path.basename(diamond_file).split('.diamond.')[0]
I am not sure of the exact source of the error.The text was updated successfully, but these errors were encountered: