Download clade definitions from GitHub #154
Merged
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.
Description of proposed changes
Remove local copies of clade and subclade definitions for H1N1pdm, H3N2, and Vic and add configuration and rules to download these files from the corresponding GitHub repositories as needed by each workflow. This approach allows us to maintain local copies of clades and subclades for Yam and other exceptions to the standard maintained clades. Since we only need to maintain the two "clade systems" of "clade" and "subclade" for the main phylogenetic workflow, this commit defines a top-level mapping of clade file URLs to lineages and segments. This is in contrast to the build-specific clade mappings used by the Nextclade workflow (for example).
Note that we eventually want to assign clade labels with Nextclade instead of augur clades, so this implementation should get deleted when that change happens.
Checklist