-
Notifications
You must be signed in to change notification settings - Fork 145
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
[BUG] --prodigal-single-mode
breaks metagenomic workflow
#2305
Comments
Dear @lmrodriguezr, thank you very much for reporting this and apologies for the frustration. I find this a bit confusing and I think the error is related to another problem with your anvi'o environment. The error mentions that the I double checked: anvi'o One likely solution that would solve this is to install your environment from scratch. I would suggest you to install the development version to track Best wishes, |
Hi @meren BTW, installing It looks like I'm now facing a different problem, though. CONCOCT is no longer working, and it throws the error:
Is this a known issue? I'll keep trying :) Thank you! |
Oh, never mind, I found this: #2154, and I'm now trying agin after |
This is now in the |
|
Short description of the problem
The recently introduced
--prodigal-single-mode
flag from f1291f7 causes workflows to fail with the following error:Presumably this is because the JSON files are missing the
anvi_gen_contigs_database.--prodigal-single-mode
key, but unfortunately theanvi-run-workflow --get-default-config
command doesn't include it either.I tried the workaround of just adding
anvi_gen_contigs_database.--prodigal-single-mode
manually to the JSON (see the example in the files at the bottom), but that's not recognized:anvi'o version
I'm using the github
HEAD
(this change was introduced 3 weeks ago), but here is the output anyways:System info
Rocky Linux 8.6 (Green Obsidian), using a SIF file with Singularity that I modified to Anvi'o
HEAD
. I cannot use the stable release because of a DAStool issue now solved inHEAD
.Detailed description of the issue
I believe the above (and below) cover all the details, but I'm happy to share the
SIF
if that helps.Files / commands to reproduce the issue
Config files before and after "fix" (which didn't actually fix anything): https://gist.github.com/lmrodriguezr/c60708194da15a1902258e178258afe5
The text was updated successfully, but these errors were encountered: