-
Notifications
You must be signed in to change notification settings - Fork 98
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
TRIO KP.5 (JN.1.11.1 + S:T572I) with S:R346T (84) #2568
Comments
FedeGueli
changed the title
JN.1.11.1 acquired S:T572I (15) first and then S:R346T (3) > TRIO
JN.1.11.1 acquired S:T572I (25) first and then S:R346T (3) > TRIO
May 8, 2024
FedeGueli
referenced
this issue
May 16, 2024
Designated KP.5 via dbfae34 |
FedeGueli
changed the title
JN.1.11.1 acquired S:T572I (25) first and then S:R346T (3) > TRIO
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (11) > TRIO
Jun 13, 2024
the trio branch has now 11 seqs |
FedeGueli
changed the title
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (11) > TRIO
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (14) > TRIO
Jun 20, 2024
FedeGueli
changed the title
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (14) > TRIO
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (25) > TRIO
Jul 1, 2024
FedeGueli
changed the title
KP.5 (JN.1.11.1 + S:T572I) with S:R346T (25) > TRIO
TRIO KP.5 (JN.1.11.1 + S:T572I) with S:R346T (49)
Jul 10, 2024
FedeGueli
changed the title
TRIO KP.5 (JN.1.11.1 + S:T572I) with S:R346T (49)
TRIO KP.5 (JN.1.11.1 + S:T572I) with S:R346T (84)
Aug 3, 2024
84, only 20 in July tough and with many from Canada, i think this will die off. |
FedeGueli
referenced
this issue
Oct 22, 2024
@AngieHinrichs it's unclear whether it should be KP.5 or KP.2 sublineage but since KP.2 is more dominant in terms of behaviour I put it there
Dessigntad KP.2.27 via 986687e#diff-ead4244ff49c81bc758e9f068f5ef42156bd985b9c86de8fa4d6fcd7f2829090R1209 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original KP.5 proposal
Formerly tracked as Branch 63 of https://github.com/sars-cov-2-variants/lineage-proposals/issues/1097 and for FLiRT>Trio branch as Branch 111 of https://github.com/sars-cov-2-variants/lineage-proposals/issues/1089JN.1.11.1 >S:T572I (C23277T)
Query:C7113T,C23277T,T3565C, G24872T,-G9010A,-C6070T,-A24819G,T22928C
Samples: 15
EPI_ISL_18989868, EPI_ISL_19012494, EPI_ISL_19022916,
EPI_ISL_19028021, EPI_ISL_19032236, EPI_ISL_19032824,
EPI_ISL_19038709, EPI_ISL_19055484, EPI_ISL_19055680,
EPI_ISL_19058372, EPI_ISL_19070036, EPI_ISL_19070190,
EPI_ISL_19070263, EPI_ISL_19073920, EPI_ISL_19076771
Now with a FLiRT > TRIO Branch:
KP.5 > C3811T > C2197T, C9857T, S:R346T (G22599C) ,A23080G (S:Q506Q)
New query: C3811T, G22599C,C23277T, G17334T by @aviczhl2 from sars-cov-2-variants/lineage-proposals#1724
[former Query:C3811T , C2197T, C9857T,T3565C ]
Samples: 3 (US)
Tree:
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_150f8_c372a0.json?label=id:node_6971654
The text was updated successfully, but these errors were encountered: