Add schema for unaligned sequences - #2038
Merged
Merged
Conversation
This was referenced Aug 12, 2026
Some workflows use unaligned sequences as input to augur subsample. In this case, proximal samples will not work properly. This schema makes it easier for workflows to guard against configs with proximal samples. At run time, augur subsample itself still validates configs against the default schema that allows proximal samples. This is fine because augur proximity errors if sequence lengths differ.
victorlin
force-pushed
the
victorlin/schema-subsample-config-unaligned
branch
from
August 12, 2026 18:13
6fbc6ad to
f8e00fd
Compare
joverlee521
approved these changes
Aug 12, 2026
joverlee521
left a comment
Contributor
There was a problem hiding this comment.
Unfortunate it's not easy to layer JSON schemas for this, but I think having separate schemas here is worth it for workflows!
Merged
2 tasks
This file contains hidden or 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
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.
Description of proposed changes
Some workflows use unaligned sequences as input to augur subsample. In this case, proximal samples will not work properly. This schema makes it easier for workflows to guard against configs with proximal samples.
At run time, augur subsample itself still validates configs against the default schema that allows proximal samples. This is fine because augur proximity errors if sequence lengths differ.
Related issue(s)
Checklist
Automated checks passGitHub issues