-
Notifications
You must be signed in to change notification settings - Fork 101
BA.5.2+ORF1b:T1050N sublineage circulating in China (312 seq as of 2023-01-06) #1471
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
Comments
I do not think we can conclude that the majority of the people infected by this lineage also have C11824T. If we exclude the sequences uploaded from China (which is strongly biased by the province that uploads sequences), only 11 from 18 sequences have this mutation. |
Now this counts 75 sequences if i got correctly the nucleotides gisaid query : C2710T, C8626T, T17208C. @InfrPopGen @corneliusroemer @AngieHinrichs @thomasppeacock i think a rapid designation is deserved:
|
That's an understatement - this and #1470 could together account for as many of half of all infections worldwide right now. Seems like a pretty strong case for designation. |
yeah agree. i just avoided big claims, the ones who will designate it know that very well ;) |
Correction actually it is 74 not 75 one sequence caught by Gisaid query C2710T, C8626T, T17208C is a totally unrelated bat virus from Yunnan. |
Thanks for reminding me @FedeGueli, I had removed that sequence from the initial count but then forgot about it. |
nevermind it was a fault of mine. |
96 viruses as today |
102 viruses as today two new ones from India and one from California |
Thanks @silcn. I will try to fix that today. |
157 viruses as today. well represented in Shangai too. An exception to the not NUC only rules should be done to designate it . otherwise our work in tracking sublineages of it will be much harder . |
I had to permanently exclude Japan/PG-356772/2022|EPI_ISL_15261684|2022-09-06 to stop matOptimize from splitting up T17208C, but it's intact in the 2022-12-30 tree. [Not the initial version that rolled out at 7pm Pacific time yesterday, but an updated version from this morning that rolled out at 7am.] |
182 sequences as today. new upload from Bejing today |
216 as Now . Mass upload from Pechino plus more sequences from American airports. |
@thomasppeacock @corneliusroemer @InfrPopGen @AngieHinrichs the tree of this one looks like this now, and after the great catch by @silcn also its three proposed sublineages seem very well supported and there is one more unproposed: Indeed I proposed to designate everything in a row: then its main branches: |
233 sequences as today: new samples come from Italy , Spallanzani institute. |
253 sequences as the BF.7 they are now appearing in mass. |
2 new sequences from Japanese airport surveillance. |
280 as this evening , several sequences uploaded from Singapore: 7 from airport surveillance but also 12 local cases. |
300 as today it seems highly prevalent in the first samples from Hunan |
312 as today last samples coming from England Denmark Italy and India. |
Added new lineage BA.5.2.48 from #1471 with 217 new sequence designations, and 0 updated
Thanks for submitting. We've added lineage BA.5.2.48 with 217 newly designated sequences, and 0 updated. Defining mutations T17208C, C16887T (following C8626T). |
FYI 16887 is masked in the UShER tree because it is in https://github.com/W-L/ProblematicSites_SARS-CoV2 . [ah, I see @silcn already noted that in the original proposal!] |
I noticed this, it is worth mentioning: #1474 is circulating in Japan |
I have updated the correct issue. It should be #1478 instead of #1474. |
Proposal for a sublineage of BA.5.2.
Earliest seq: 2022-10-05 (Guangdong, China)
Countries detected: Singapore (16, including 9 travellers from China and 2 travellers from Hong Kong), China (7, all from Guangdong), Cambodia (1), England (1, yet to be uploaded to GISAID)
Mutations on top of BA.5.2:
G12310A, ORF1b:T1050N, C27012T, C27513T (the main branch of BA.5.2+ORF1b:T1050N)
then C2710T, then C8626T, then C16887T+T17208C (note C16887T is extremely homoplasic so doesn't show up on Usher)
GISAID query: nuc mutations C2710T, C8626T, T17208C
This is one of two major lineages that appear to be circulating in China, along with the BF.7 lineage in #1470. Like that lineage, it was present in China long before the end of the zero-Covid policy and therefore appears to be growing as the result of a founder effect. ORF1b:T1050N is the only AA mutation that distinguishes this from BA.5.2, but as BA.5.2+ORF1b:T1050N was never designated, I believe this lineage should still be eligible for designation.
The majority of the sequences in this lineage also have C11824T. Due to a single sequence from Japan on the C2710T+C8626T branch containing this mutation, along with the masking of C16887T, Usher has split the lineage into two separate branches on the tree, one with C11824T and one without. It's pretty clear that Usher has got this wrong.
Usher tree for sequences with C11824T:
https://nextstrain.org/fetch/github.com/silcn/subtreeAuspice1/raw/main/auspice/subtreeAuspice1_genome_2c776_9157f0.json?branchLabel=Spike%20mutations&c=gt-nuc_17208&label=id:node_7079342
Usher tree for sequences without C11824T:
https://nextstrain.org/fetch/github.com/silcn/subtreeAuspice1/raw/main/auspice/subtreeAuspice1_genome_2c8a3_915a30.json?branchLabel=Spike%20mutations&c=gt-nuc_17208&label=id:node_7079778
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?variantQuery=nextcladePangoLineage%3ABA.5.2*+%26+%5B5-of%3A+G12310A%2C+ORF1b%3AT1050N%2C+C27012T%2C+C27513T%2C+C2710T%2C+C8626T%5D+%26+C16887T+%26+T17208C&
EPI_ISLs
EPI_ISL_16181562
EPI_ISL_16181568
EPI_ISL_16259461
EPI_ISL_16259462
EPI_ISL_16259465
EPI_ISL_16259469
EPI_ISL_16259474
EPI_ISL_16259475
EPI_ISL_16259477
EPI_ISL_16259479
EPI_ISL_16259481
EPI_ISL_16259483
EPI_ISL_16259489
EPI_ISL_16259494
EPI_ISL_16259504
EPI_ISL_16259506
EPI_ISL_16264215
EPI_ISL_16264216
EPI_ISL_16264219
EPI_ISL_16264220
EPI_ISL_16264221
EPI_ISL_16264222
EPI_ISL_16264223
EPI_ISL_16274001
The text was updated successfully, but these errors were encountered: