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

Roary is not working with bakta-generated gff3-files #284

Open
LindavdGvB opened this issue Apr 24, 2024 · 1 comment
Open

Roary is not working with bakta-generated gff3-files #284

LindavdGvB opened this issue Apr 24, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@LindavdGvB
Copy link

Roary is not working with the gff3-files generated with Bakta whereas Roary works well with the by Prokka generated gff3 files.
The roary warning is:
2024/04/24 10:55:41 Fixing input GFF files

--------------------- WARNING ---------------------
MSG: ##feature-ontology header tag parsing unimplemented

2024/04/24 10:55:43 Input files have identical MD5 hashes, only using the first file

There are two issues about this on the Roary github site, but since Roary works well with the Prokka generated gff3 files, I assume that this is an issue of Bakta.
sanger-pathogens/Roary#598
sanger-pathogens/Roary#583

@LindavdGvB LindavdGvB added the bug Something isn't working label Apr 24, 2024
@oschwengers oschwengers added help wanted Extra attention is needed and removed bug Something isn't working labels Apr 28, 2024
@oschwengers
Copy link
Owner

@LindavdGvB , thanks for reporting. Could please try to install Roary in a fresh conda environment? There are reports that this seems to be related to outdated Perl packages that Roary depends on. As we have successfully tested Roary with Bakta generated GFF3s in the past, I guess it's actually an issue with Roary and older Perl packages than a Bakta issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants