Skip to content
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

Closed
Sinickle opened this issue Jan 9, 2023 · 9 comments
Closed

XBC.2 sublineage with S:K444T [19 seqs, Australia] #1538

Sinickle opened this issue Jan 9, 2023 · 9 comments

Comments

@Sinickle
Copy link

Sinickle commented Jan 9, 2023

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
image

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.
image

Genomes: EPI_ISL_15871036, EPI_ISL_16048844, EPI_ISL_16360629, EPI_ISL_16315535, EPI_ISL_16074134, EPI_ISL_16133825, EPI_ISL_16134171

@Sinickle Sinickle changed the title XBC.2 sublineage with S:K444T [7 seqs, Australia] XBC.2 sublineage with S:K444T [9 seqs, Australia] Jan 17, 2023
@FedeGueli
Copy link
Contributor

@Sinickle Sinickle changed the title XBC.2 sublineage with S:K444T [9 seqs, Australia] XBC.2 sublineage with S:K444T [11 seqs, Australia] Jan 21, 2023
@Sinickle Sinickle changed the title XBC.2 sublineage with S:K444T [11 seqs, Australia] XBC.2 sublineage with S:K444T [13 seqs, Australia] Jan 24, 2023
@corneliusroemer corneliusroemer changed the title XBC.2 sublineage with S:K444T [13 seqs, Australia] XBC.2 sublineage with S:K444T [16 seqs, Australia] Jan 29, 2023
@corneliusroemer
Copy link
Contributor

This is still around - 16 sequences now, let's keep watching

@corneliusroemer
Copy link
Contributor

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:

  • 5584 and 25000 are either problematic sites in Philippino sequences or the Philippino sequences are ancestral and 5584G and/or 25000T mutated later
  • It'd also be good to figure out what the XBC ancestral state was at 1437, 1758, 10029. One should plot the hypothetical donors and XBC.1/2 next to each other and see what it shows

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.

@FedeGueli
Copy link
Contributor

FedeGueli commented Feb 12, 2023

@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)
and then it has G4184A =(orf1a:G1307S) that is present in 668K sequences of BA.5.2, this points to a possible recombiantion event XBC/BA.5.2 for this proposed lineage

Schermata 2023-02-13 alle 00 19 47

Schermata 2023-02-13 alle 00 19 14

Schermata 2023-02-13 alle 00 24 25

https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_33ef7_967be0.json?branchLabel=back-mutations&c=gt-nuc_1437,5584,8353,10029&label=id:node_8623057

@Sinickle
Copy link
Author

@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

@corneliusroemer
Copy link
Contributor

Just stumbled over C1758T being present in BF.7.16. Does that tell us anything or just a coincidence?

@FedeGueli
Copy link
Contributor

Where is BF.7.16 circulating? could be one of those very hard to verify recombinants with a BkP in NSp1-2?

@Sinickle
Copy link
Author

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.

@Sinickle Sinickle changed the title XBC.2 sublineage with S:K444T [16 seqs, Australia] XBC.2 sublineage with S:K444T [17 seqs, Australia] Feb 14, 2023
@Sinickle Sinickle changed the title XBC.2 sublineage with S:K444T [17 seqs, Australia] XBC.2 sublineage with S:K444T [19 seqs, Australia] Mar 14, 2023
@corneliusroemer
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants