-
Notifications
You must be signed in to change notification settings - Fork 97
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
BA.2.75.5 (S:K356T) sublineage with S:R346T, S:490S [8 seqs as of 2022-09-01, IN, JP, AT, SGP, UK] #994
Comments
Given the geographic spread, I'd be really surprised if we don't see a lot more of this in the coming weeks. For such a unique constellation of mutations to appear all at once in such distant locations, it seems likely this sublineage is fairly widespread in some undersequenced region. |
We need new issues to either have an epidemiological event or be close to exhibiting an epidemiological event before opening. Will therefore close this one for now |
Hi @chrisruis the cluster carries Spike_R346T, Spike_F490S, Spike_K356T. These are major sites according the Bloom lab Escape calculator for SARS-CoV-2 RBD.
Would this not qualify as an "event of epidemiological significance" (https://www.pango.network/the-pango-nomenclature-system/statement-of-nomenclature-rules/)? "(vi) The clade may carry a set of multiple mutations of particular biological interest or concern. Note that, in most cases, the presence of a single specific mutation, by itself, will not be considered sufficient to warrant a new lineage designation." |
Good question @agamedilab - with that rule we're typically looking for something a bit more divergent. 3 mutations of interest may lower the threshold compared with 1 but we'd still want to see another epidemiological event to designate, particularly in this case expansion over co-circulating lineages |
@chrisruis besides the 3 spike mutations mentioned above the cluster alos carries ORF1a:H110Y, ORFa:M3627I and ORF3a:T229I plus G11146T. No need to designate it right away but does the set of mutations not warrant monitoring? |
We only really want an issue to be opened for a clade once it's at least close to being able to be designated, 4 sequences isn't enough in this case |
8 seq. from 5 countries (Asia: Singapure, Japan, India; Europe: Austria England) on Usher as of 31.08.22. Expansion into England, India with yesterdays upload.
|
If this is not worth an express designation, what is? BA.2.75.2 with similar set of concerning mutations AND far-ranging intercontinental presence (#963) was designed straight away and rightly so, since it is now the fastest-growing lineage of all. |
3 more sequences including an end of July one from Telangana
|
Actually there seems to be one more from England that isn't yet on GISAID (Usher pulls from COG-UK directly): I think this is worth designating due to the convergent mutations, fast growth and clear branch it's on. |
Agree on the reopening of this issue and a fast designation we have seen already with vaccine update toward Omicron , a clear early communication of what is new and fast or not is of utmost importance (Example: @josetteshoenma spotted first BA.2 was faster than BA.1 earlier last Xmas day while sci comm was skeptical ) |
+1 from the Netherlands: EPI_ISL_14773227
|
There is another one from the Netherlands. I believe I missed it yesterday, because GISAID calls it a BA.2. But Nextclade calls it BA.2.75.5 and it has all the mutations, as far as I know. EPI_ISL_14775779 from 2022-08-11 That brings the total from my query at 11. |
I see there is an English one that isn't on GISAID yet, so 12 then. |
Designated as BN.1 with 10 sequences (I excluded the one Japanese one as it had a lot of reversions to reference) |
In the last 2 days, 4 BA.2.75* with a triple spike mutation on top of the polytomy have showed up in:
1x Japan (ex Thailand)
1x Singapore
2x Austria
GISAID query:
Spike_K356T, Spike_F490S, Spike_R346T
Collection dates all past 12th of August 2022.
We've seen all these Spike mutations before but not in this combination. It's not clear in which sequence these mutations occurred.
Usher places these under BA.2.75.5 (with S:R356T) so I'd say we make it a sublineage of that.
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_1303e_8c5920.json?branchLabel=aa%20mutations&label=nuc%20mutations:A22629C
The clustering is very clear, the branch nice and long. Let's hope that we don't see more of this lineage in the next few days.
The text was updated successfully, but these errors were encountered: