-
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
New XBB.1 sublineage with S:F486P orf1a:K120R , - likely emerged from Malaysia -25 sequences - Singapore, Japan, #1654
Comments
two new samples from Japan and Singapore. |
2 new sequences uploaded from Malaysia (the first directly sampled there) confirming initial.hypothesis this arose in Malaysia |
10 sequences as today. Last samples from elderly people in Singapore (local cases) |
Now the tree has competely changed so i am editing the proposal to start this lineage with: justified by the following tree: https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_3d48_a49000.json?c=userOrOld&label=id:node_7760413 15 sequences Gisaid query: @corneliusroemer @InfrPopGen @AngieHinrichs @thomasppeacock i ve broaden this proposal . Although low numbers they deserve a check, the area is dense of XBB.1*486P variants they should be designated to be distinguished btw slow and fast ones |
20 samples of this one, two new samples from two different district of Japan |
25 sequences as today . Last samples from Japan and Singapore, one of them with travel history from Philippines. |
Lineage notes and the git commit log say this is XBB.1.5.27, which makes sense as the next-available designation, but this has been added to the XBB.1.27 milestone instead of the XBB.1.5.27 milestone. |
This is indeed a mistake, the latest specified branch in the subbranch of XBB.1 is currently XBB.1.23, while the latest specified branch in the subbranch of XBB.1.5 is XBB.1.5.27 |
It should be XBB.1.24 (without T17124C) |
It hs been designated XBB.1.5.27 , just the milestone is uncorrect. About the fact to be a broader xbb.1.5 descendant or XBB.1 independent 486P acquisition i tend to think the second is more likely cause its geographical origin from Malaysia is quite well documented , but too few evidence to state it is not a broader xbb.1.5 descendant for certain t |
Sorry - I made a mistake here. It should indeed be XBB.1.24 and not XBB.1.5.27 - I messed up somewhere along the way. I'm fixing. |
Please remove XBB.1.27 milestone makes a bit mess when searching for it! |
_EDITED ON 09-03-23
Now the tree has competely changed so i am editing the proposal to start this lineage with:
Orf1:K120R (A624G)> S:F486P, C27297A
justified by the following tree:
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_3d48_a49000.json?c=userOrOld&label=id:node_7760413
15 sequences
Gisaid query:
A624G,C27297A,T23018C
has to be noticed that all the three "branches of this sublineage have additional spike mutations we have seen in variant soup at S:255 and s:256 but also at S:158 as Delta (but different AA)_
ORIGINAL proposal:
Put here to simplify the work in monitoring XBB.1 * 486P sublineages.
This is totally independent from the others already designated.
it carries two additional defining mutations: Orf1a:K120R , Orf1a:k261N beyond S:F486P
Tree:
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_430f4_a60ea0.json?c=userOrOld&label=id:node_9610401
Gisaid query:NSP1_K120R,NSP2_K81N, Spike_F486P
it has to be highlighted that one sample (with travel history from Malaysia) has also S:255F,S:T678P and N:E136Q
Sequences:
EPI_ISL_16847528, EPI_ISL_16899415, EPI_ISL_16899433 all of them have been sampled in Singapore and in February 2023
( 2 imported into Singapore from Malaysia, one local case in an elderly man)
Defining mutations:
Orf1:K120R (A624G) then Orf1a:K261N G1048T), C27297A, S:F486P (T23018C)
The text was updated successfully, but these errors were encountered: