-
Notifications
You must be signed in to change notification settings - Fork 128
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
feat(ancestral): Add optional Nextclade GFF3 compatibility mode #1664
Open
corneliusroemer
wants to merge
7
commits into
master
Choose a base branch
from
nextclade-compat
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Commits on Nov 10, 2024
-
feat(ancestral): Add optional Nextclade GFF3 compatibility mode
Until this PR, it was hard to use augur ancestral with a genome annotation gff3 from a Nextclade dataset for multiple reasons: - The GFF reader in augur looks for "gene" features only, while Nextclade 3 uses primarily CDS (gene only for backwards compatibility) - Augur's GFF reader doesn't support compound features - It takes the "gene"/"feature" name in the order "gene" > "gene_name" > "locus_tag", which differs from Nextclade's order This meant that users had to create a Genbank file, just for the purpose of running augur ancestral. That was doable but tedious. This PR solves the problem by adding a new GFF reader mode that is designed to be as compatible with Nextclade as possible. That means: - It looks for CDS features (for simplicity it ignores Nextclade's gene backwards compatibility) - It supports compound features - It takes the feature name in the exact same order as Nextclade The new mode is activated by passing the `--nextclade-compatibility` flag to augur ancestral. It does no harm to anyone who does not want to use it. It results in some code duplication, but I think it's totally worth it for the sake of usability. I have already started using it in some of my private builds and it works like a charm.
Configuration menu - View commit details
-
Copy full SHA for 26f18b7 - Browse repository at this point
Copy the full SHA 26f18b7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 46d2f81 - Browse repository at this point
Copy the full SHA 46d2f81View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4571e59 - Browse repository at this point
Copy the full SHA 4571e59View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5d8fe73 - Browse repository at this point
Copy the full SHA 5d8fe73View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6e96773 - Browse repository at this point
Copy the full SHA 6e96773View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1280a95 - Browse repository at this point
Copy the full SHA 1280a95View commit details -
Configuration menu - View commit details
-
Copy full SHA for 566150e - Browse repository at this point
Copy the full SHA 566150eView commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.