Open aviczhl2 opened 1 month ago
@aviczhl2 LP.1.1 is not LP.1 + S:R190S , designation of https://github.com/sars-cov-2-variants/lineage-proposals/issues/1664 is still pending. Please correct that!
@aviczhl2 please add branch 25 of #1502 and also this one ah i see it is already branch 8, it has been tracked in #1502 in the comments some weeks ago.
Also branch 21 of #1502 should be added here ()
Also branch 21 of #1502 should be added here ()
already branch 4 of this sorry.
i ve added (lineage) for branches of other issues to make easier to identify them
it should be all ok now. thanks for this important tracking issue.
cc @dailycovidcases please wait a bit before proposing them separately: at least wait them to reach 30 seqs
br 6 edited to exclude the Bat viruses
Br 8 jumped to 11 Br.6 to 8 Br.7 to 6 Br.9 to 5
Br 8 jumped to 11 Br.6 to 8 Br.7 to 6 Br.9 to 5
As said all branches are fastly growing.
New 31del+190S branch this time from Russia and on JN.1.4 backbone: JN.1.4.5>> T18453C > Orf8:S103L (C28201T) > C11020T > S:R346T (G22599C) >> S:S31del (Del21653-55) S:K147E (A22001G), S:R190S (G22132T), A28058G, N:G236D (G28980A) Query:A22001G,G22132T, A28058G Samples: 3 Russia Saint Petersburg tree:
cc @aviczhl2
New 31del+190S branch this time from Russia and on JN.1.4 backbone: JN.1.4.5>> T18453C > Orf8:S103L (C28201T) > C11020T > S:R346T (G22599C) >> S:S31del (Del21653-55) S:K147E (A22001G), S:R190S (G22132T), A28058G, N:G236D (G28980A) Query:A22001G,G22132T, A28058G Samples: 3 Russia Saint Petersburg tree: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_45e73_97bd30.json?label=id:node_7141875
cc @aviczhl2
Shall be recombinant of JN.1.4.5 and branch 18 of #1502 ? Is C11020T convergent?
No it has T18453C isn't it? That blocks chances of simple recombs with 1 or 2 BPs.
I checked and C11020T is very convergent. So the Russian one is a new branch.
I checked and C11020T is very convergent. So the Russian one is a new branch.
Yeah i was thinking the same
Br.6 to 13 Br.7 to 7 Br.8 to 13 Br.9 to 7 all growing
@aviczhl2 i suggest to track all of them here not in #1502, i mean the count and the query here not there
Add branch 12, LB.1+S:R190S direct branch
Add branch 13 and 14.
Branch 14 is very interesting it stems out of the Jn.1+C25566T branch that is the branch leading then to JN.1.7 so i suspect it is either old one or some sort of recombinant, it is also misplaced in a 28603T branch that got FLipFLopped then
ah and it is 4 on Usher with a Uk Climb sample too
@aviczhl2 please propose branch 6 and branch 8
Add branch 15-17. Branch 17 is interesting, JN.1 with raw add-ons DeFLiRT+S:R190S without any other things, 5 seqs detected in 4 countries.
Branch 12 becomes 15.
Branch 8 designated JN.1.59.1 via https://github.com/cov-lineages/pango-designation/commit/699fb71616e45ddde4f74e0af21644fda0c4ef24
Add branch 18, KP.2.3 with S:478T reversion, S:R190S and 2-nuc Orf1a:1973S. detected in India local and GBW from India and UAE.
New old branch from Brazil:
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice24_genome_test_4b277_5129e0.json?label=id:node_7230994 i have excluded the flip flop C28603T from the defining. JN.1 >> C25566T >S:A67V (C21762T),S:R190S (G22132T), G25494T, ORF3a:A110S (G25720T), C29119G > S:R346T (G22599C) , S:S31del (del21653-55) My query is : G22132T, G25494T,del21653 Samples : 3 (5 on Usher) most recent sampled on 6/21 so it is not recent.
New old branch from Brazil: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice24_genome_test_4b277_5129e0.json?label=id:node_7230994 i have excluded the flip flop C28603T from the defining. JN.1 >> C25566T >S:A67V (C21762T),S:R190S (G22132T), G25494T, ORF3a:A110S (G25720T), C29119G > S:R346T (G22599C) , S:S31del (del21653-55) My query is : G22132T, G25494T,del21653 Samples : 3 (5 on Usher) most recent sampled on 6/21 so it is not recent.
That's Branch 14.
Branch 17 seems having a lot of seqs and merged with LF.7 on usher(due to usher unable handling deletions) now.
Top: LF.7 Bottom: Branch 17.
@AngieHinrichs, this is another example of a branch without deletion merged with a deletion branch. (the others include KP.1.1.1 and https://github.com/cov-lineages/pango-designation/issues/2649, LB.1 and LB.1.8, KP.2.3 and https://github.com/cov-lineages/pango-designation/issues/2722)
Add branch 19 and branch 20
Branch 16 becomes 12 Branch 7 becomes 11
Branch 17 seems having a lot of seqs and merged with LF.7 on usher(due to usher unable handling deletions) now.
Top: LF.7 Bottom: Branch 17.
@AngieHinrichs, this is another example of a branch without deletion merged with a deletion branch. (the other is KP.1.1.1 and cov-lineages/pango-designation#2649)
To me it is ok enough tp broaden LF to 190S and then differentiate in the lineages with 31P and 31del
Ping @corneliusroemer
Branch 17 seems having a lot of seqs and merged with LF.7 on usher(due to usher unable handling deletions) now. Top: LF.7 Bottom: Branch 17. @AngieHinrichs, this is another example of a branch without deletion merged with a deletion branch. (the other is KP.1.1.1 and cov-lineages/pango-designation#2649)
To me it is ok enough tp broaden LF to 190S and then differentiate in the lineages with 31P and 31del
Ping @corneliusroemer
The trajectory is clearly different. It is not likely for R190S to appear before S31del or T22N. They have to be separate lineages.
Branch 17 seems having a lot of seqs and merged with LF.7 on usher(due to usher unable handling deletions) now. Top: LF.7 Bottom: Branch 17. @AngieHinrichs, this is another example of a branch without deletion merged with a deletion branch. (the other is KP.1.1.1 and cov-lineages/pango-designation#2649)
To me it is ok enough tp broaden LF to 190S and then differentiate in the lineages with 31P and 31del Ping @corneliusroemer
The trajectory is clearly different. It is not likely for R190S to appear before S31del or T22N. They have to be separate lineages.
yeah but if usher keeps them together wee can also decide to follow it without making things harder, at the end every decision is conventional reinforced by likelyhood or parsimony.
Br.9 now 14 and BR.12 now 24, please propose it if all of the new samples belong to it, i suspect may be some new -s should be needed for both these branches
yeah but if usher keeps them together wee can also decide to follow it without making things harder, at the end every decision is conventional reinforced by likelyhood or parsimony.
It uses a false likelihood not considering deletions, resulting in bad assignment.
yeah but if usher keeps them together wee can also decide to follow it without making things harder, at the end every decision is conventional reinforced by likelyhood or parsimony.
It uses a false likelihood not considering deletions, resulting in bad assignment.
i mean if there is not a nuc mutation that makes a lineage needed to be moved elsewhere , how does it matter if placed here or there? likely LF.7 is not Jn.1.16 but unrleated but as @corneliusroemer explained some lineages have been designated as JN.1.16 derivatives, and for sure JN.1.16 itself collects some independent acquisition of T22928C, but if this doesn't impact our work i dont see any issue with that. Consider that time of the few people involved in variant tracking and more importantly in designations, nextclading etc is limited, i think if there is no clear difference the easiest thing is the best one.
Br.9 is 9 after adding more -s , Br.12 is still at 21 from various countries after excluding those. Propose Br.12.
Also add branch 21.
Also add branch 21.
The query doesnt work apparently
Also add branch 21.
The query doesnt work apparently
Sorry, shall be G14023A, query edited
Add branch 22.
There should be a branch with 190S under Lb.1.3.1 , two samples collected on July 22 from two countries Denmark, France Query:G22132T, C24382T, G25290T LB.1.3.1 >> S:R190S (G22132T), C24382T, S:C1243F (G25290T) the French sample has gained also S:D111N and S:T1116N suggesting circulation in some undersampled zone. tree:
There should be a branch with 190S under Lb.1.3.1 , two samples collected on July 22 from two countries Denmark, France Query:G22132T, C24382T, G25290T LB.1.3.1 >> S:R190S (G22132T), C24382T, S:C1243F (G25290T) the French sample has gained also S:D111N and S:T1116N suggesting circulation in some undersampled zone. tree:
Added as branch 23.
Branch 18 becomes 7 with new samples from India and GBW from China.
Add branch 24, another KP.2.3+S:S31-, S:K478T rev,S:R190S, 5 GBW seqs from Botswana, UAE, Qatar and Dominician Republic
Add branch 25.
@aviczhl2 the 478T parent of BR.24 has been proposed?
Branch 23 becomes 4 ,with 2 more from NZL
Add branch 26, another KP.4.2+S31-+R190S, detected in Japan and UK, as well as GBW from Pakistan
Add branch 27.
Branch 9 becomes 14. Add branch 28.
Updated query for Branch 3 : -C3885A,-C1909T,-T24079C,-T14508C,-T13123C,A24819G,G22132T,4999,T3565C finds 54 Now proposed in https://github.com/cov-lineages/pango-designation/issues/2755
Usher tree changes for Branch 24 and now it becomes 9 and includes an Indian seq.
BR.18 to 9 both new samples from New Jersey
It seems that there is a new convergent mutation of S:R190S. It usually couples with S:S31del.
Cov-spectrum shows its growth is negative with S:S31S, but large growth advantage with S:S31-. It seems that like S:Q493E must be gained after S:F456L, this S:R190S must present under S:S31- variants.
https://cov-spectrum.org/explore/World/AllSamples/Past2M/variants?variantQuery=S%3A31S&aaMutations1=S%3AR190S%2CS%3A31S&analysisMode=CompareToBaseline& https://cov-spectrum.org/explore/World/AllSamples/Past2M/variants?variantQuery=S%3A31-&aaMutations1=S%3AR190S%2CS%3AS31-&analysisMode=CompareToBaseline&