Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate clade definitions and lineage definitions #71

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

trvrb
Copy link
Member

@trvrb trvrb commented Jun 18, 2022

I didn't like how in the the live version we have a mixture of "clades" like MPXV Clade 1 and "lineages" like B.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 for hmpxv1.

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

Screen Shot 2022-06-18 at 4 15 33 PM

This commit separates clade definitions used for mpxv from lineage definitions used for hmpxv1.

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
@trvrb trvrb self-assigned this Jun 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

1 participant