schemas: Extend export v2 schema to support an array of trees #851
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Supports the new multi-tree or exploded tree features in Auspice, while maintaining backwards compatibility. Resolves #848.
Closed
|
@jameshadfield's example JSON file in #848 fails on master but passes on this branch when tested with: https://data.nextstrain.org/zika.json continues to pass. |
jameshadfield
added a commit
that referenced
this pull request
Apr 24, 2024
Multiple trees ("subtrees") have been available in Auspice since late
2021¹ and part of the associated schema since early 2022². Despite this
there was no way to produce such datasets within Augur itself, and
despite the schema changes the associated `augur validate` command was
never updated to allow them.
This commit adds multi-tree inputs to `augur export v2` as well as
allowing them to validate with our associated validation commands.
¹ <nextstrain/auspice#1442>
² <#851>
jameshadfield
added a commit
that referenced
this pull request
Apr 24, 2024
Multiple trees ("subtrees") have been available in Auspice since late
2021¹ and part of the associated schema since early 2022². Despite this
there was no way to produce such datasets within Augur itself, and
despite the schema changes the associated `augur validate` command was
never updated to allow them.
This commit adds multi-tree inputs to `augur export v2` as well as
allowing them to validate with our associated validation commands.
¹ <nextstrain/auspice#1442>
² <#851>
jameshadfield
added a commit
that referenced
this pull request
May 6, 2024
Multiple trees ("subtrees") have been available in Auspice since late
2021¹ and part of the associated schema since early 2022². Despite this
there was no way to produce such datasets within Augur itself, and
despite the schema changes the associated `augur validate` command was
never updated to allow them.
This commit adds multi-tree inputs to `augur export v2` as well as
allowing them to validate with our associated validation commands.
¹ <nextstrain/auspice#1442>
² <#851>
jameshadfield
added a commit
that referenced
this pull request
May 6, 2024
Multiple trees ("subtrees") have been available in Auspice since late
2021¹ and part of the associated schema since early 2022². Despite this
there was no way to produce such datasets within Augur itself, and
despite the schema changes the associated `augur validate` command was
never updated to allow them.
This commit adds multi-tree inputs to `augur export v2` as well as
allowing them to validate with our associated validation commands.
¹ <nextstrain/auspice#1442>
² <#851>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Supports the new multi-tree or exploded tree features in Auspice, while
maintaining backwards compatibility.
Resolves #848.