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

BUSCO gff file(s) not captured in output when Augustus used, no errors as stderr suppressed #6132

Open
Hymenium opened this issue Jul 8, 2024 · 1 comment

Comments

@Hymenium
Copy link

Hymenium commented Jul 8, 2024

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.

cat busco_galaxy/run_*/busco_sequences/*busco_sequences/*.gff >> busco_output.gff 2> /dev/null || true

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

@Hymenium 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
@igormakunin2
Copy link

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants