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

Proposal for new lineage within B.1 #6

Closed
anthonypwest opened this issue Feb 11, 2021 · 7 comments
Closed

Proposal for new lineage within B.1 #6

anthonypwest opened this issue Feb 11, 2021 · 7 comments
Labels
designated proposed Proposal for a new lineage
Milestone

Comments

@anthonypwest
Copy link

Description

Sub-lineage of: B.1
Earliest sequence: 2020-11-23
Most recent sequence: 2021-01-29
Countries circulating: A lineage predominantly circulating in New York but with a few exports to other countries. Characterised by spike mutations T95I and D253G, plus others.
The most frequent spike mutation pattern is L5F T95I D253G E484K D614G A701V, with a smaller fraction having S477N instead of E484K.

Other common coding changes in this lineage are:
N P199L M234I
NS3 P42L Q57H
NS8 T11I
NSP2 T85I
NSP4 L438P
NSP6 S106del G107del F108del
NSP12 P323L
NSP13 Q88H

Genomes
B.1.XX_genomes.txt

List of genomes, collated 2021-02-10, attached.

Evidence

Phylogenetic tree (PDF and image). Spike mutations and bootstrap values are indicated. Proposed new lineage includes all sequences except for those in the grey shaded box at the top.
B.1.XX_tree_spike_mutations.pdf

B 1 XX_tree_image

Phylogenetic tree file:
B.1.XX_tree.txt

Proposed lineage name

To be determined as the the next available designation within B.1

@aineniamh
Copy link
Member

Hi Anthony, thanks for posting the issue. We've just tagged a new release of the lineage designations here that include this new lineage as B.1.526.

This lineage, with the sequences you've mentioned here, will get added into the pangoLEARN model training today. When that's finished a new release of pangoLEARN will be tagged here and the website updated.

Thanks again, going to now mark this issue as resolved.

@anthonypwest
Copy link
Author

anthonypwest commented Feb 11, 2021 via email

@AngieHinrichs
Copy link
Member

AngieHinrichs commented Feb 11, 2021 via email

@anthonypwest
Copy link
Author

anthonypwest commented Feb 11, 2021 via email

@rambaut
Copy link
Contributor

rambaut commented Feb 11, 2021

There are two problems with giving a sublineage for the 484K carrying genomes - the first is that the 484K is the only defining mutation and with other lineages we have seen 484K coming up multiple times independently (for example with the B.1.1.7 variant in the UK we have had more than 5 independent cases of 484K). The second is, as you point out, this is all in one geographical area. If it was any other mutation it would not qualify. I think we will hold off for now.

@aineniamh
Copy link
Member

Agree with what Andrew said, but I'm happy to add the line as you requested @anthonypwest to give more information about that particular lineage.

@anthonypwest
Copy link
Author

anthonypwest commented Feb 11, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
designated proposed Proposal for a new lineage
Projects
None yet
Development

No branches or pull requests

4 participants