Closed HynnSpylor closed 3 months ago
I'm not convinced that the French sequence in that tree is from the same parent. since I believe all of the mutations prior to its S:346i are actually pretty common in JN.1.
However, the Sweden, Australia, and Italy sequences appear to be related, despite that they contain a different mutation on S:346. A query of just "C11747T, C20629T" will return those 3 as the only JN.1 sequences. They also have regular expected BA.2.86 mutations in the area surrounding 346 (332, 356) so I don't think it's contamination.
At least the Australia and Italy sequences must represent onwards transmission of an S:346 mutation.
Also notable - the Italy sequence has a reversion on S:408, which is allegedly covered.
4th sequence for the query C11747T, C20629T -- France, R346T. As it stands, the 3 of them with R346T are...
Australia - Nov 4 Italy, France - Nov 6
Up to 6 seqs now with C11747T, C20629T.
All but one are with S:R346T. Australia - Nov 4 Italy, France x2 - Nov 6 Sweden - Nov 13
This should be moved to the main page, imo.
EDIT: I'm mistaken. One of the French sequences doesn't have S:R346T or S:R346i, so the query I'm using here isn't perfect now.
Correct list with R346T is
Australia - Nov 4 Italy, France - Nov 6 Sweden - Nov 13
@HynnSpylor please propose it
SCcratch this one:
The query for S:R346T is C11747T, C20629T,G22599C finds 5 https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_13bf8_214840.json?label=id:node_4467378
Other S:R346T popping up: 1 G10540T, C22088T 1 seq from Belgium with S:176F
2 C21952T,G22599C,C11747T,C1762A 1 seq from France
3 this one without a specific query
all the trees from :https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_13bf8_214840.json?c=userOrOld&label=id:node_4467536
It seems that several branches get S:R346T. I decide to arrange it and change the title as "Multiple JN.1+R346X Branches"
It seems that several branches get S:R346T. I decide to arrange it and change the title as "JN.1+R346X Branches"
Ok thank you. in the comments you cna find some query i found for the other branches/singlets.
Transferred from #1118
There are around 40 JN.1 that have S:R346T, but most of them are poor quality sequences with lots of XBB mixed in.
When filtering out those pretty clear artefacts, we're left with 11-12 BA.2.86 that may actually have 346T. These are shown in the screenshot, where mutations are shown with respect to BA.2.86 parent, that's why there are so few mutation markers:
Interestingly, most of the 346T are within JN.1 (9 out of 11), much more concentrated than we'd expect by chance (around 1/4 of total BA.2.86 are JN.1 in GISAID).
Within JN.1, 8 out of 9 are on the JN.1 branch with C1762A (ORF1a:F499L) and C11747T. Again more concentrated than one would expect by chance (around 40% of JN.1 are on that branch).
4 out of those 8 share another mutation that's seen only once elsewhere within JN.1: C20629T (ORF1b:H2388Y).
Thus, it looks like at least these 4 sequences form a proper monophyletic lineage that could get designated. Though the numbers are still a bit small and there's a contamination issue as evidenced by the 3/4 of BA.2.86 + 346T being likely artefacts:
hCoV-19/Australia/NSW-ICPMR-50850/2023|EPI_ISL_18513742|2023-11-04
hCoV-19/Sweden/D-6556154176/2023|EPI_ISL_18538246|2023-11-13
France/GES-IPP26802/2023|EPI_ISL_18540862|2023-11-06
Italy/LOM_Unimi-3855-23/2023|EPI_ISL_18510429|2023-11-06
GISAID query: G22599C,C20629T,C11747T,C1762A
It's also possible that the 8 sequences are a single event - better wait for sequence numbers to double before making a decision. Due to the way the other 4 are scattered around, they look like independent events for now, though.
On Usher, things are a bit messy:
Here's how Nextclade arranges things with just the 346T sequences on the JN.1 branch:
Let's just track this one here for now, these collection issues can get overwhelming. This one is the biggest and clearest and most likely to be conclusive soon.
I think this is a fifth one for the 20629T cluster:
hCoV-19/France/PAC-HCL723001520801/2023|EPI_ISL_18545255|2023-11-06
Further ones compatible with a single 346T even preceding C20629T rather than following:
hCoV-19/France/IDF-IPP26423/2023|EPI_ISL_18522061|2023-11-05
hCoV-19/France/ARA-CHUGA-3118929452/2023|EPI_ISL_18536531|2023-11-16
So we are at 5 (7) sequences for this cluster. The biggest question now is whether to designate broadly (not requiring 20629T) or narrowly (requiring it). We should know within a week.
Thank you @corneliusroemer !
Further ones compatible with a single 346T even preceding C20629T rather than following:
hCoV-19/France/IDF-IPP26423/2023|EPI_ISL_18522061|2023-11-05 hCoV-19/France/ARA-CHUGA-3118929452/2023|EPI_ISL_18536531|2023-11-16
Yes they are the ones i couldnt find a query for, i think they could be really one same lineage.
Thx @corneliusroemer @FedeGueli !
@corneliusroemer maybe also Switzerland/ZH-UZH-IMV-47c6ebf0/2023|EPI_ISL_18541794|2023-11-13 belongs to the ones that could belong to this together with the two additional french sequences: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_5ee2b_5c3250.json?c=userOrOld&label=id:node_4470384
New 20629T: hCoV-19/France/PAC-HCL723001570001/2023|EPI_ISL_18568815|2023-11-13
, so 6 now
Extra ones compatible with event directly on polytomy:
hCoV-19/France/IDF-IPP26423/2023|EPI_ISL_18522061|2023-11-05
hCoV-19/France/ARA-CHUGA-3118929452/2023|EPI_ISL_18536531|2023-11-16
hCoV-19/Belgium/Jessa_11-2346-001845/2023|EPI_ISL_18566124|2023-11-14
hCoV-19/France/OCC-HCL723001552101/2023|EPI_ISL_18568662|2023-11-13
Making it 10 for that case. If it keeps going like this, we'll designate directly on the polytomy. Let's wait a few more days.
R346I at 4
Branch 2 at 6 (+1 Illinois)
Branch 1 at 7 Branch 2 at 8 R346I at 5 while the branch stemming out from the politomy is 7 : https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_1c90d_99edf0.json?c=gt-S_346&gmax=25384&gmin=21563&label=id:node_4444768
cc @corneliusroemer still low numbers
Branch 1 > 8 branch 2 > 10 S:R346I > 8
Branch 1 > 12 Branch2 > 16 S:R346I > 15 S:R346S > 5
Branch 1 > 12 Branch 2 > 16 S:R346I > 13 S:R346S > 5
Branch 1 > 18 branch 2 > 17 R346I > 13 R346S > 5
they seem quite slow.
I would like to recapitulate current situation looking at the downsampled tree:
I can determine as separate branches: JN.1.1 Branch 1:JN.1.1 >C11747T>G22599T (S:R346I), then further >C20629T> (ORF1b:H2388Y)>T22599C (S:I346T) query: C20629T, G22599C, T22926C Samples 18
Branch 2 : JN.1.1 > C11747T > C9142T > S:R346T (G22599C) then A18600G , S:Q173H (G22081T) Query: C11747T, C9142T ,G22599C,C1762A Samples: 17
Branch 3: JN.1.1 > C11747T >S:R346T (G22599C) Query: -G4720A,-C21952T,C11747T,G22599C, -C9142T,-C20629T,C1762A,-T3488C Samples: 18
Branch 4 : JN.1.1 > C11747T > T3488C > S:r346T (G22599C) Query : T3488C,C11747T,G22599C,C1762A
JN.1 Branch 5: JN.1 > S:R346T (G22599C), G22627A Query : G22599C, G22627A,C18894T ,T3565C Samples: 25
Branch 6: JN.1 > > S:R346T (G22599C) Query: Query: C18894T ,T3565C,G22599C,-C1762A,-G22627A,-C774T,-C2536T,-C27371T,-T21973C,-C2395T,-C5654T,-C18687T,-C19145A, -C6040T,-T20241C,-T21738C,-A9935G,-C1938T,-A28795G,-C19944T Samples : 27 (? - The query still catches unrelated samples)
Branch 7: Jn.1 > S:R346T G22599C, Orf6:P57L :C27371T Query: G22599C, C27371T,C18894T ,T3565C Samples : 9
Branch 8: JN.1 > C2536T, S:R346T (G22599C) Query: C2536T, G22599C,T3565C Samples: 4
Branch 9: JN.1 > A12928G, 17301C, T21973C, S:R346T (G22599C),ORF3a:Q213K (C26029A), ORF7a:T28I (C27476T)
Query: A12928G, 17301C, T21973C,
Samples : 3
Branch 10: JN.1 > C2395T, G17562T, S:R346T (G22599C) Query: C2395T, G22599C,C18894T Samples : 3
Branch 11: JN.1 > C5654T, C9763T , C7840T, S:R346T (G22599C) Query: C5654T, C9763T , C7840T Samples: 3
I left out for now the branches under Orf1a:T170I i will add in the following weeks
Many branches now are growing (B1-2-3-5-7)
Branch 1 designated JN.1.1.3 via https://github.com/cov-lineages/pango-designation/commit/f240a76716a6cdf8dcbd15a8f8dbb924f2dd06a1 Branch 5 designated JN.1.6.1 via https://github.com/cov-lineages/pango-designation/commit/5625be4ba186f79501d0700e666ca6af702b0f4e
added branch 12
added branch 13 (that has both JN.1.3 and JN.1.1 defining so it could be either one of them.)
Branch 6 is 89 now
Branch 6 is 89 now
Thanks it unluckily collects all the new samples outside the branches excluded. ping @corneliusroemer maybe a planned designation of mayor reamianing branches could help?
added branch 14 from https://github.com/cov-lineages/pango-designation/issues/2464
Branch 6 is 230 now
Branch 6 is 230 now
thx checking if it collects unrelated sample now.
@aviczhl2 a lot of new things also in combo w 572I stay tuned!
Branch 6 is 230 now
New query excluding multiple lineages found 209. very likely it is around 200 seqs . cc @corneliusroemer
Also Branch 2 and Branch 3 and Branch 14 going up.
Added branch 16: Jn.1.4+346T from Jap/Sing.
Branch 6 at 230 with the query now quite good ( i ve excluded some recombinant with excluding orf8:8*
Added a NZL branch with 346I and 622I from NZL
here the S:R346I trees popping up in JN.1 , highly homoplasic too:
Branch 6 designated JN.1.18 from https://github.com/cov-lineages/pango-designation/commit/425fe95872f894f6f168ec62796929defd8bef47
@FedeGueli proposes the JN.1.7+R346K branch https://github.com/sars-cov-2-variants/lineage-proposals/issues/1371
now 22 branches
I ve added branch 23 : cc @corneliusroemer i ve missed to add this one until today cause i mistook it for another branch with Orf3a:G18D include in the multiple 572I lineages. I count at least 10 countries for it and it has been sampled in Kenya and in a traveller from Ghana this makes me think to a solid prevalence in african continent, hence i suggest direct designation of it.
Moreover one recent sample from England got also S:K304N that worked well in XBB.1.16
Added branch 28. @corneliusroemer it is a 15ish sequence lineage emerging from India (KA,MH) and already exported to Uk and US.
Added branch 29 . cc @corneliusroemer and @angiehinrichs could you take. a look at this ? it is misplaced to JN.1.1 but has orf1a:499 reverted, it has S:T22I, S:Q23H and S:Q183R beyond 346T but on Gisaid the nuc query with these mutations fails to catch any , while it works if i take the node from 346T ahead :
Added Branch 35 this one is interesting cause coming from Peru'
Deleted branch 39 cause it is part of branch 7 :
@corneliusroemer i will propose in the next fe hpours three branches each of them emerged in an under sampled area
Rearranged Branch 9 , the query caught just a singaporean cluster of JN.1.8 while now it is 19 and widespread in different countires added branch 41 456L+346T new query for Branch 37 that gained s:f456L
Added branch 29 . cc @corneliusroemer and @AngieHinrichs could you take. a look at this ? it is misplaced to JN.1.1 but has orf1a:499 reverted, it has S:T22I, S:Q23H and S:Q183R beyond 346T but on Gisaid the nuc query with these mutations fails to catch any
The S:T22I and S:Q23H are artefacts and will be masked starting in tomorrow's build (2024-02-20), hopefully that will fix it. Unless you think the S:Q183R is also incorrect?
Added branch 29 . cc @corneliusroemer and @AngieHinrichs could you take. a look at this ? it is misplaced to JN.1.1 but has orf1a:499 reverted, it has S:T22I, S:Q23H and S:Q183R beyond 346T but on Gisaid the nuc query with these mutations fails to catch any
The S:T22I and S:Q23H are artefacts and will be masked starting in tomorrow's build (2024-02-20), hopefully that will fix it. Unless you think the S:Q183R is also incorrect?
Thanks @AngieHinrichs i think it is real , lets see what happens when the update will be up!
Intro
**i think the original proposal should be updated in this way** (_Edited and Updated_ BY MOD): I would like to recapitulate current situation looking at the downsampled tree: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_test_19c8e_3c4600.json?label=id:node_6806774 I can determine as separate branches:Branch 1: Now designated JN.1.1.3
Branch 2 : Now designated JN.1.1.5 from https://github.com/cov-lineages/pango-designation/issues/2492
Branch 3: Broadened to JN.1.1.3 via https://github.com/cov-lineages/pango-designation/commit/0c19ec354cacce2f1703927bc9d863947e9afba3
Branch 4 : canceled it is not monophyletic
Branch 5: now designated JN.1.6.1
Branch 6: now designated JN.1.18
Branch 7: Designated JN.1.44.1
Branch 8: dead
Branch 9: Designated JN.1.8.2 from https://github.com/cov-lineages/pango-designation/issues/2495
Branch 10: dead
Branch 11: Dead
Branch 12 : Dead
Branch 13 : Dead
Branch 14 : Designated JN.1.13.1
Branch 15: Designated JN.1.7.3
Branch 16: now proposed in https://github.com/cov-lineages/pango-designation/issues/2601
Branch 17: Slow
Branch 18: Dead
Branch 19: Dead
Branch 20: designated JN.1.7.1 from #1371
Branch 21 : Designated KQ.1
Branch 22 : Dead
Branch 23: Designated LE.1 and LE.1.1
Branch 24: Now proposed in https://github.com/cov-lineages/pango-designation/issues/2602
Branch 25: Dead
Branch 26 : Dead
Branch 27: Dead
FLiRT Branch 28:Designated JN.1.30.1 from https://github.com/cov-lineages/pango-designation/issues/2514
With further FLIRT S:F456L branch Designated KU.2
Branch 29 :Dead
Branch 30 Dead
Branch 31 Dead
Branch 32 FLIRT now proposed in https://github.com/cov-lineages/pango-designation/issues/2557
Branch 33 Dead
Branch 34 :Now Designated JN.1.26
Branch 35 : Designated JN.1.42.2
Branch 36: Designated JN.1.48.2
Branch 37 designated JN.1.24.1 from https://github.com/cov-lineages/pango-designation/issues/2520
Branch 38 Dead
Branch 39: REMOVED
Branch 40: designated LC.1
FLIRT Branch 41: Designated JN.1.16.1
Branch 42: Dead
Branch 43 : Dead
Branch 44 : Dead
Branch 45 : REMOVED:
FLIRT Branch 46 : Designated KP.1.1 spotted by @aviczhl2 from in https://github.com/cov-lineages/pango-designation/issues/2510
Branch 47: dead
Branch 48: Dead
Branch 49 : Excluded
Branch 50: Dead
Branch 51: Designated JN.1.39.1
FLIRT Branch 52: designated KP.4.2 from https://github.com/cov-lineages/pango-designation/issues/2523
FLIRT Branch 53: desingated KP.4.1 from https://github.com/cov-lineages/pango-designation/issues/2521
FLIRT Branch 54: Designated KP.2
Branch 55 found by @corneliusroemer designated JN.1.25.1
Branch 56 spotted by @krosa1910 FLIRT designated KZ.1.1 from #2548
Designated KZ.1.1.1
Branch 57 thx to @DailyCovidCases i noticed that this is not monophyletic at all, among the lineages caught by query the most interesting is this one JN.1.4 >> T18453C > C7732T>> Orf1a:D4117N (G12614A) > G22111A > C27944T >S:T22N (C21627A ) > S:R346T (G22599C) > A17256G, S:F58L (T21734C ) Query: A17256G, T21734C Samples: 12 (US) Tree: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_601bd_fe5200.json?label=id:node_7136106 Original:
Branch 58 now designated JN.1.4.4 thx to @aviczhl2 that highlighted me the new JN.1.4 tree.
Branch 59 Dead
Branch 60: Dead
Branch 61 Designated JN.1.11.2
FLIRT Branch 62 Designated JN.1.9.2 & LB.1 from https://github.com/cov-lineages/pango-designation/issues/2546
Branch 63 FLiRT first spotted by @aviczhl2 now proposed in https://github.com/cov-lineages/pango-designation/issues/2562
Branch 64: Duplicate it was KZ.1.1.1
Branch 65: FLiRT spotted and proposed by @aviczhl2 in #1445 (https://github.com/cov-lineages/pango-designation/issues/2530)
Branch 66 Dead
FLiRT branch 67 Dead
FLiRT Branch 68 dead
Branch 69 Dead
Branch 70 : Dead
Branch 71 : Tracked now in #1462
Branch 72 dead
Branch 73 FLiRI> dead
Branch 74 : Undersampled area needed to check if dead
Branch 75 : Dead
Branch 76 FLiRI Designated LA.2 from https://github.com/cov-lineages/pango-designation/issues/2555
Branch 77 dead
Branch 78 FLiRT: dead
Branch 79 Dead
Branch 80 Dead
Branch 81 Dead
Branch 82 Dead
Branch 83 Dead
Branch 84 Designated LQ.1 and LQ.1.1
Branch 85 FLiRT now proposed in https://github.com/cov-lineages/pango-designation/issues/2606
Branch 86 DEAD
Branch 87 JN.1.18.4
Branch 88 dead
Branch 89 Designated JN.1.56.1
Branch 90 spotted and proposed by @aviczhl2 in #1503 #2679
Branch 91 : Designated KW.1.1.1 and LG.1
Branch 92 : Dead
Branch 93 DEAD
Branch 94 FLiRT Now proposed in https://github.com/cov-lineages/pango-designation/issues/2565
Branch 95 Dead
Branch 114 Now designated KP.2.9 TRIO former Singlet 22 = Branch 96
Branch 97 proposed in #1682
Branch 98
Branch 99 FLiRT now proposed in https://github.com/sars-cov-2-variants/lineage-proposals/issues/1648
Branch 100 FliRT now proposed in https://github.com/cov-lineages/pango-designation/issues/2583
Branch 101 JN.1.18.5
Branch 102 Dead
Branch 103 Dead
Branch 104 Dead
Branch 105 Dead
Branch 106 Dead
Branch 107 MP.1 and MP.1.1
Branch 108 now proposed in https://github.com/cov-lineages/pango-designation/issues/2605
Branch 109 Spotted and proposed by @aviczhl2 As branch 62 of #1253
Branch 110 Dead
Branch 111 now designated Kp.2.27
Branch 112: Proposed in https://github.com/cov-lineages/pango-designation/issues/2645
Branch 113 KR.3 see branch 87 of # 1253
Branch 114 Duplicate now KP.2.9
Branch 115 Dead
Branch 116 Dead
Branch 117 Dead
Branch 118 Dead
Branch 119 Dead
Branch 120 Designated KR.2
Branch 121 Dead
Branch 122 : Dead
Branch 123 dead
Branch 124 Designated LF.3
Branch 125: Designated LV.2 it is a MOV lineage- intercontinental
Branch 126: It has now split in two: one proposed in https://github.com/sars-cov-2-variants/lineage-proposals/issues/1623 with A22108C, C23277T, T23599C and the other tracked as Branch 149
Branch 127: Dead
Branch 128 Dead
Branch 129 TRIO duplicate of Branch 126
Branch 130 Dead R346T
Branch 131 Dead
Branch 132 dead
Branch 133 designated LF.6
Branch 134 Proposed in https://github.com/cov-lineages/pango-designation/issues/2659
Branch 135 FLIRT NOW DESIGNATED JQ.2.1.1 VIA https://github.com/cov-lineages/pango-designation/commit/1ff69c9ea3d7baf3bdb7db3563e1f425aa109b61
Branch 136 designated MH.1
Branch 137 designated MF.1 proposed in https://github.com/cov-lineages/pango-designation/issues/2461
Branch 138 now designated LU.1
Branch 139 Designated LM.1
Branch 140 dead
Branch 141 ex singlet 50 dead
Branch 142: dead
Branch 143 Dead
Branch 144 dead
Branch 145 dead
Branch 146 proposed in https://github.com/cov-lineages/pango-designation/issues/2677
Branch 147 Designated LZ.2 via https://github.com/cov-lineages/pango-designation/commit/2c6deafbe1cc1a52cd7c282d9bd5719189962d0c
Branch 148: dead
Branch 149 (ex branch 126) now proposed in https://github.com/sars-cov-2-variants/lineage-proposals/issues/1755
Branch 150 ex singlet 25 Fvirt designated MB.1
Branch 151 Dead
Branch 152 dead
Branch 153 Now proposed in https://github.com/sars-cov-2-variants/lineage-proposals/issues/1773
Branch 154 Designated MJ.1 JN.1.29.1 > S:R346T > Orf1a:E2070K (G6473A), T17364C, S:S31P ( T21653C) Query: G6473A, T21653C,A9935G Samples: 19 (Likely from Latin America)
BRANCH 155 now designated MQ.1
FLIRT Singlets (also FVIRT or FLIRI or FLIRS):
1) transferred to Branch 63
2) Dead
3) Now Branch 110
4) Now it became Branch 102
5) Now Branch 94
6) Dead
7) Dead
8) Now Branch 100
9) Now Branch 92
10) Dead
11) Proposed in https://github.com/cov-lineages/pango-designation/issues/2596
12) now Branch 97
13) As expected it conflated then in Branch 63
14) Now Branch 93
15) Now Branch 94
16)Dead
17) Dead
18) Now Branch 51
19) Dead
20) Now Branch 95
21) Now proposed by @Sinickle in #1504
22) Now Branch 96 Now designated KP.2.9
23) Now Branch 98
24) Dead
25) now Branch 150
26) Now Branch 97 with Singlet 12
27) Dead
28) TRIO now JN.1.48.1+ 572I spotted and proposed by @aviczhl2 in https://github.com/cov-lineages/pango-designation/issues/2547 Query: C23277T,C25378T, T3913
29) Dead
30) Now Branch 115
31) Dead
32)Dead
33) Now Branch 112 ( = Branch 73 of #1253 found by @aviczhl2 )
34) Dead
35) Now Branch 133
36) Dead
37) Proposed in #2493
38) Now Branch 143
39) Now Branch 116
40) Dead
41) Dead
42) Dead
43) Now Branch 125
44) Dead
45) XDK/JN.1.11.1 recombinant spotted by @JosetteSchoenma Query: T2950A, C18115T, G24872T
46) Now Branch 144
47) Dead
48) Dead
49) Dead
50) Dead
51) Dead
52) Dead
53) Dead JN.1.11.1 > Orf1a:T4087I (C12525T) > ORF1a:S2030L (C6354T), A13237T, Orf1b:K2557R (A21137G), A21694G, S:R346T(G22599C), S:Q675H (G23587C), S:D1146E (T25000G) Query: C6354T, A13237T,T3565C (Scotland)
54) Dead
55) Dead
56) now Branch 127
57) Dead
58) Dead
59) Dead
60) Dead FViRT JN.1 > Orf1a:G519S (G1820A) > S:A288S (G22424T) > S:R346T (G22599C) > A13992G, G17562T, C19524T S:F456V (T22928G) Query: A13992G, G17562T, C19524T (UAE)
61) Proposed in https://github.com/sars-cov-2-variants/lineage-proposals/issues/1678
62) Now Branch 136
63) Dead
64) Now Branch 131
65) Dead
66) Dead
67) Dead
68) Dead
69) Now Branch 141
70) Dead
71) Now Branch 136 DelTRIO (First ever) LB.1+S:S31Del > S:T572I (C23277T)
Query:C23277T,G22111T , G22599C , T22928C,del21653 (Israel)
72) Now Branch 138
73)Dead
74) Dead
75) Dead
76) Dead
77) Dead
78) Designated JN.1.50
79) Now Branch 135
80) Dead
81) Branch 134 now
82) Dead
83) Now Branch 145
84) JN.1.11.1 > C29095T > G18816T, S:R346T (G22599C), S:N641S (A23484G), T24073C Query: G18816T, A23484G, T24073C (Spain)
85) JN.1 > A871G, T3172G,C1170T, T17859C, S:R346T (G22599C), S:F456L (T22928C) Query:A871G, T3172G,C1170T (Spain)
86) now proposed in #1571
87) FLiRI JN.1.29 > S:F456L(T22928C) > T8053C > Orf1b:1588C (A18230G), S:R346I (G22599T), Orf3a:D155H (G25855C) Query: A18230G, G25855C (Finland)
88) JN.1.4> C5284T >S:F456L (T22928C) > S:R346T(G22599C), Query: C6433A, T22928C, T18453C,G22599C S.Korea likelyy misplaced under br.89 of #1253
89) Now Branch 147
Singlets will be no more tracked since May 21.
Interesting Singlets:
1) Dead >sibling of branch 79 JN.1.4 > T18453C > T4342C, C5869T, T17154C, Orf1b:A1662V (C18452T) > S:R346T (G22599C) Query: T4342C, C5869T, T17154C,G22599C NY Now **2** 2)Dead >JN.1 > C23896G > C186T > A19782G > C829T, Orf1a:T2093I (C6543T), S:L293I (C22439A), S:R346K (G22599A), S:S884F (C24213T) Query: C829T, C6543T, G22599A NY 3)Dead >JN.1.4 > C25710T > C28312T +346T +456L UK Query: C27791T ,C20178T, G22599C, T22928C 4)Dead >JN.1.33 > Orf1a:Y1846C (A5802G)> C3092T, S:R346K (G22599A) Query: C3092T ,G22599A,T3565C 5) Proposed in # 2560 PANGO >JN.1> Orf1a:N2147S (A6705G) > T24892C > Orf1a:S135R>K (G669A), Orf1a:I368T (T1368C), C4189T, Orf1a:Y1619H (T5120C), S:R346T (G22599C), A24241G, N:N192D(A28847G) Query:G669A, T1368C, C4189T:::::::::::::::::::::::::::::::
Original proposal
Branch 1 Defining mutations: JN.1>T3565C>T27810C(ORF7b:F19L)>C1762A (ORF1a:F499L)>C11747T>G22599T (S:R346I), then further >C20629T> (ORF1b:H2388Y)>T22599C (S:I346T) for R346I GISAID query: A6183G, G22599T for R346T GISAID query: C20629T, G22599C, T22926C _Alternative query by Cornelius for 346T_: G22599C,C20629T,C11747T,C1762A (**edited**) Earliest seq: 2023-10-02 (France- EPI_ISL_18412591) Most recent seq: 2023-11-06 (Italy- EPI_ISL_18510429) Countries detected: R346I seqs: France (1), Sweden (1) R346T seqs: Italy (1), Australia (1) Usher Tree: ![QQ截图20231117202709](https://github.com/sars-cov-2-variants/lineage-proposals/assets/121703496/a7f2e9de-db57-4440-8045-a38752a3eab9) https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_293e4_7364f0.json?c=gt-S_346 S:R346 is a key site and S:R346T was successful in BF.7*, BQ.1.1*, CH.1* and recently XBB* lineages. Nowadays JN.1* is the fastest growing lineage, while this JN.1* branch has a two-step evolution as S:R346I>T. We can see how the R346I/R346T work on the JN.1 seqs. Genomes: R346I: EPI_ISL_18412591, EPI_ISL_18489980 R346T: EPI_ISL_18510429, EPI_ISL_18513742 ****************************+ Branch 2 Defining : JN.1.1 > C11747T > C9142T > S:R346T (G22599C) then A18600G , S:Q173H (G22081T) Query: C11747T, C9142T ,G22599C,C1762A Samples: 5 IDs: EPI_ISL_18552979, EPI_ISL_18553493, EPI_ISL_18577478, EPI_ISL_18577484, EPI_ISL_18577493 [Tree](https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_65447_db1820.json?c=gt-S_346&gmax=25384&gmin=21563&label=id:node_4493811)