-
Notifications
You must be signed in to change notification settings - Fork 422
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
BUSCO gff file(s) not captured in output when Augustus used, no errors as stderr suppressed #6132
Comments
Hymenium
changed the title
BUSCO gff file(s) not captured in output, no errors as stderr suppressed
BUSCO gff file(s) not captured in output when Augustus used, no errors as stderr suppressed
Jul 8, 2024
We observed a similar issue, an empty gff file from Busco Galaxy Version 5.7.1+galaxy0, on Galaxy Australia. Busco. An early version of Busco, Galaxy Version 5.5.0+galaxy0, produces a valid (non-empty) gff file on the same nucleotide sequences. Both versions produce an empty gff file on protein sequences, but I don't know if gff output supported for protein inputs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Despite >90% of BUSCOs being matched in a genome, the buso_output.gff file is empty.
I'm not sure why this cat command doesn't get the contents of the .gff files. The path looks fine and the run_*/busco_sequences folder seems to be there, but error messages are redirected.
tools-iuc/tools/busco/busco.xml
Line 86 in bc94851
It seems that it works when MetaEuk is selected but not Augustus.
I can't submit a bug report but here is a history demonstrating the issue on some tutorial data: https://usegalaxy.eu/u/hymenium/h/busco-gff-test
The text was updated successfully, but these errors were encountered: