-
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
XBC.2 sublineage with S:K444T [19 seqs, Australia] #1538
Comments
I think we are at 12 samples now: https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_21b65_b256b0.json?c=userOrOld&label=id:node_8382490 This is worth to be designated. |
This is still around - 16 sequences now, let's keep watching |
It's still at 16 sequences, but it's really interesting. Just found it again when looking at potential Delta containing recombinants. This must involve another recombination even of some sort, maybe a bit like BA.1/2/4/5. It's complex, also tricky because Philippino sequences often have dropouts, and Australia-WA has some artefacts as well. If anyone wants to figure out what happened here, would be great. A few points from a bit of an investigation:
This recombinant shows some traits of XBC.2 but has 1758 like XBC.1. The explanation is possibly not so complicated as long as one figures out what are artefacts and what isn't. |
@corneliusroemer really messy thing it is harder to disentangle what could be artifact and what could be real, i would like to highlight that this proposed lineage has C1627T and then a reversion =orf1a:V498A =(T1758C) |
@FedeGueli that could be it, from what I can tell! I also found these sequences which are XBC with the same two mutations you mentioned. They don't seem to be ancestral to my proposed lineage though, and they also seem to carry an additional nucleotide mutation that could be from BA.5.2 -- C5575T |
Just stumbled over C1758T being present in BF.7.16. Does that tell us anything or just a coincidence? |
Where is BF.7.16 circulating? could be one of those very hard to verify recombinants with a BkP in NSp1-2? |
I don't think BF.7.16 having C1758T is related, unless I'm misunderstanding your point? The proposed lineage has T1758C, which is a reversion from how XBC.2 normally is. |
Designated as XBC.2.1 - too unclear whether this is a recombinant and if so of which lineages. So for simplicity this is XBC.2.1 - also makes it easier to keep track of than if this was a recombinant. |
Description
Sublineage of: XBC.2
Earliest sequence: 2022/11/02/ Australia/ Western Australia
Most recent sequence: 2022/12/22 / Australia / Western Australia
Countries circulating: Australia - Western, Victoria, Tasmania
Mutations on top of XBC.2:
Spike- K444T
ORF1a - V498A (reversion), G1307S
ORF8 - A15T
Nucleotides: C222T, C1627T, G4184A, C9541T, A22893C, G27936A, T1758C (reversion), T23086C (reversion)
GISAID query: spike_f486p,spike_k444t, spike_k97r
cov-spec query: s:486p, s:444t, s:97r
USHER Tree
Evidence
Spike_K444T has appeared on highly successful lineages such as BQ.1 and CH.1.1.
XBC has not acquired K444T and L452M on the same branch yet, but if these are both independently successful mutations, it's possible they show a way that XBC can gain further advantage in the future and possibly stay relevant.
I think it's odd that this has reversions relative to XBC.2, which has reversions relative to XBC. I think this shows that we likely did not designate the true XBC ancestor, and that my proposed lineage is also not a true descendant of XBC.2, but rather is a sibling lineage to it.
Genomes: EPI_ISL_15871036, EPI_ISL_16048844, EPI_ISL_16360629, EPI_ISL_16315535, EPI_ISL_16074134, EPI_ISL_16133825, EPI_ISL_16134171
The text was updated successfully, but these errors were encountered: