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

Potential new BA.5.X lineage in Asturias (mainly) #618

Closed
VirologiaHUCA opened this issue May 10, 2022 · 20 comments
Closed

Potential new BA.5.X lineage in Asturias (mainly) #618

VirologiaHUCA opened this issue May 10, 2022 · 20 comments
Assignees
Milestone

Comments

@VirologiaHUCA
Copy link

Description
Sub-lineage of: BA.5
Earliest sequence: 2022-04-15
Most recent sequence: 2022-04-29
Countries circulating: Spain, Denmark, England, Scontland, Canada
<written description of the proposed lineage, where it is circulating, when, why it is distinct>
In BA.5 variants, this clade gained the nsp16_V288F mutation. Subsequently, the clade gained a new mutation, nsp6_V289L.
Genomes
<list of genome names as found on GISAID or accession ids - provide as a CSV/TSV table attachment - include locations and dates of sampling>

EPI_ISL_12406393
EPI_ISL_12207803
EPI_ISL_12291987
EPI_ISL_12472550
EPI_ISL_12473106
EPI_ISL_12151839
EPI_ISL_12434927
EPI_ISL_12477595
EPI_ISL_12283695
EPI_ISL_12490468
EPI_ISL_12589393
EPI_ISL_12589394
EPI_ISL_12589398
EPI_ISL_12589400
EPI_ISL_12589402
EPI_ISL_12589404
EPI_ISL_12589405
EPI_ISL_12589406

Evidence
<image from phylogenetic tree?>
image

@FedeGueli
Copy link
Contributor

FedeGueli commented May 11, 2022

@corneliusroemer i gave a look at this one:

I think, when the time for BA.5 sublineages will come , this could be interesting to be designated starting with Orf1b:2685F, considering the tree starting from that mutation i found 51 seqs on covspectrum mainly from Spain, Uk, Denmark.
https://cov-spectrum.org/explore/World/AllSamples/Past3M/variants?aaMutations=S%3A486V%2COrf1b%3A2685F&aaMutations1=S%3A486V%2COrf1b%3A2685F&
But the Usher tree points to 59 seqs:
Schermata 2022-05-11 alle 23 10 43
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_23d50_c128a0.json?branchLabel=aa%20mutations&c=country&label=nuc%20mutations:A28330G

The branch leading to this sublineage has 5 nuc mutations acquired likely during sustained circulation in SA or elsewhere: A28330G then C1627T then A27038G then T6979G then C22879T
then it acquired T4690C and Orf1b:2685F and then Orf1a:V3858L this last one represents the beginning of local circulation in Spain (even if there is also a spanish sample with Orf1b:2685F alone)

@silcn
Copy link

silcn commented May 11, 2022

This is a sublineage of the big branch proposed by @corneliusroemer in #551 which is currently labelled as "monitor". I'm not sure there's a strong case for designating #551 but any decision about this lineage should be made together with a decision about that one.

@FedeGueli
Copy link
Contributor

Thx @silcn for highlighting that there are three BA.5 big branch, the one you proposed from portugal with orf10:37F, the other (double?) you mentioned there with orf1a:556K and the last one you mentioned here with nuc mut at 28330 that shows a bigger diversity than the other two. So probably designating it could catch in a better way future sublineages like this 'spanish' one that seems circulating in a sustained way.
And that was the idea of @corneliusroemer to identify early big branches to have a clear picture from the start.

@corneliusroemer
Copy link
Contributor

I think the one proposed is the green one at the top?
The yellow is #551
image

@VirologiaHUCA
Copy link
Author

Yes, this is the new linage proposed,

@FedeGueli
Copy link
Contributor

95 seqs as today

InfrPopGen added a commit that referenced this issue May 30, 2022
Added new lineage BA.5.4 from #618 with 64 new sequence designations, and 31 updated designations from BA.5.2
@InfrPopGen
Copy link
Contributor

Thanks for submitting. We've added lineage BA.5.4 with 64 newly designated sequences, and 31 updated designations from BA.5.2. Defining mutation(s) G11837T (ORF1a:V3858L), G21520T.

@InfrPopGen InfrPopGen self-assigned this May 30, 2022
@InfrPopGen InfrPopGen added this to the BA.5.4 milestone May 30, 2022
@VirologiaHUCA
Copy link
Author

VirologiaHUCA commented May 30, 2022 via email

@silcn
Copy link

silcn commented May 30, 2022

@InfrPopGen, shouldn't this be a sublineage of BA.5.2 rather than getting its own BA.5.* designation?

@FedeGueli
Copy link
Contributor

FedeGueli commented May 30, 2022

Agree with @silcn it is a sublineage of BA.5.2 and the parental of this starting from C1627T was proposed in #657. As @agamedilab noted in that issue, there is another branch starting with C1627T and if it keeps circulating, and it is likely given the BA.5 Advantage,
then it would be hard to resolve the designations properly.

Mention from #657:

"This variant is a sublineage of recently designated BA.5.2 defined by Orf9b:D16G (#551). At the moment the variant BA.5 +ORF9b:D16G, C1627T, A27038G is similar but not equivalent to BA.5.2 (i.e. c. 21% of BA.5 +ORF9b:D16G do not carry C1627T, A27038G). Therefore i leave this post open for the case that further subdivision of BA.5.2 becomes necessary (e.g against the subclade defined by G12310A):

grafik

https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_5099_462230.json?branchLabel=nuc%20mutations&c=gt-nuc_12310&label=nuc%20mutations:A28330G"

@InfrPopGen InfrPopGen reopened this Jun 1, 2022
@VirologiaHUCA
Copy link
Author

First, the proposed clade does not have the ORF9b:D16G mutation. We have tried to download some strains from the tree to compare and it has been impossible.

@agamedilab
Copy link

@VirologiaHUCA Hi, have you checked for A28330G?

ORF9b:D16G = A28330G but apparently Nextfclade bugs out when displaying ORF9b:D16G but A28330G should work (see also #657)

All the best!

@FedeGueli
Copy link
Contributor

Yes it has A28330G see the second comment in the issue and following ones from @silcn and other parental issue from @corneliusroemer

@VirologiaHUCA
Copy link
Author

Apologies, the orf9b:D16G nomenclature has misled us, we have the A28330G mutation that would be orf9a:D16Dusing orf9a reference from GISAID . As soon as we can obtain the sequences of proposals #657 and #551 we will be able to give a definitive answer

@InfrPopGen InfrPopGen added on hold on hold until parental issue resolved and removed designated labels Jun 2, 2022
@InfrPopGen
Copy link
Contributor

Thank you all for pointing out the BA.5.2 root of this lineage. Apologies for the delay in getting back to this (UK is having national holidays). I will check the 551 -> 657 ancestry and then re-designate.

InfrPopGen added a commit that referenced this issue Jun 2, 2022
Added new lineage BF.1 from #618 with 1 new sequence designations, and 94 updated designations from BA.5.2.1
@InfrPopGen
Copy link
Contributor

Re-designated as lineage BF.1 with 1 newly designated sequence, and 94 updated designations from BA.5.2.1. Defining mutation(s) G11837T (ORF1a:V3858L) (nsp6:V289L).

@InfrPopGen InfrPopGen added designated and removed on hold on hold until parental issue resolved labels Jun 2, 2022
@InfrPopGen InfrPopGen removed this from the BA.5.4 milestone Jun 2, 2022
@InfrPopGen InfrPopGen added this to the BF.1 milestone Jun 2, 2022
InfrPopGen added a commit that referenced this issue Jun 2, 2022
Withdrawn BA.5.4 as sublineage of BA.5.2.1 (issue #618), in lineage_notes.txt
@FedeGueli
Copy link
Contributor

FedeGueli commented Jun 4, 2022

@AngieHinrichs
Copy link
Member

broadening BF.1 to Orf1b:2685F and designated sublineages from there

That seems fine to me, both G21520T > G11837T and G21520T > G26122A have a good number of sequences from Spain.

@InfrPopGen InfrPopGen reopened this Jun 5, 2022
InfrPopGen added a commit that referenced this issue Jun 5, 2022
Expanded BF.1 from #618 to include sister clade that lacks G11837T but has G21520T
@InfrPopGen
Copy link
Contributor

BF.1 has now been broadened by moving root one node pastwards (nt:G21520T (ORF1ab:V7086F)); this causes 95 designations updated from BF.1 and 59 designations updated from BA.5.2.1.

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

7 participants