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

Add support to parse antiSMASH v6 results #531

Merged
merged 2 commits into from Jan 14, 2021

Conversation

reslp
Copy link
Contributor

@reslp reslp commented Jan 14, 2021

Hi Jon,

I realized that AntiSMASH has started to transition to version 6 just recently. I have therefore added support to parse this correctly. Basically I followed what you did to distingush between v4 and v5. From what I saw v6 format is not different from v5 (yet). However with the missing elif to catch v6 results will not be parsed and funannotate annotate fails at the diamond crosslinking step with MIBig because antismash output files are empty.

I have tested the code and it works. Antismash V6 results are parsed correctly and funannotate annotate also completes without error.

Hope this helps!

all the best,

Philipp

reslp and others added 2 commits January 14, 2021 18:30
If parsing v5 and v6 is the same, we can just change the logic of that one line to include all versions >5.
@nextgenusfs
Copy link
Owner

Awesome @reslp -- I simplified to just capture versions >= 5. Can you test if this works? Just a little bit less code redundancy.

@reslp
Copy link
Contributor Author

reslp commented Jan 14, 2021

Yes sure will run this again and report back. Makes sense to only use >=5 of course. I added the whole code in anticipation of possible format changes in v6. But this can be added later of course if needed.

@reslp
Copy link
Contributor Author

reslp commented Jan 14, 2021

Just tested this with only smash_version >=5. Can confirm it works.

@nextgenusfs nextgenusfs merged commit 203df27 into nextgenusfs:master Jan 14, 2021
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

Successfully merging this pull request may close these issues.

None yet

2 participants