Add segment-specific Auspice configs for 2y builds #177
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
Adds segment-specific Auspice config JSONs for 2y builds of H1N1pdm, H3N2, and Vic with custom color scales for subclades within each subtype and segment. These color scales match the scales used in the nextflu-private builds, allowing us to include the public trees in our monthly reports and easily switch between private and public trees without changing color schemes across builds. With this change, we can remove the "representative" builds from the nextflu-private build config, since the public builds already provide equal geographic and temporal sampling. Closes #164
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
Adds segment-specific Auspice config JSONs for 2y builds of H1N1pdm, H3N2, and Vic with custom color scales for subclades within each subtype and segment. These color scales match the scales used in the nextflu-private builds, allowing us to include the public trees in our monthly reports and easily switch between private and public trees without changing color schemes across builds.
With this change, we can remove the "representative" builds from the nextflu-private build config, since the public builds already provide equal geographic and temporal sampling.
Related issue(s)
Closes #164
Checklist