Separate clade definitions and lineage definitions #71
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.
I didn't like how in the the live version we have a mixture of "clades" like
MPXV Clade 1
and "lineages" likeB.1
and we call all of this "Clade". I think we need to clearly distinguish "clades" vs "lineages".This PR separates clade definitions used for
mpxv
from lineage definitions used forhmpxv1.
Additionally, this updates coloring "clade_membership" to have the display name "Lineage" for
hmpxv1
.Clades displayed for
mpxv
are:MPXV Clade 1
MPXV Clade 2
MPXV Clade 3
hMPXV-1
Lineages displayed for
hmpxv1
are:A
A.1
A.1.1
A.2
B.1
I'd think to use these as two separate columns in nextclade output as well, again labeled as "clade" vs "lineage".
Output can be seen at nextstrain.org/staging/monkeypox/hmpxv1/lineage-labels