-
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
Multiple BA.2 sublineages circulating in India: proposal for a fast designation of them to track efficiently emerging sublineages there #814
Comments
One more potentially interesting found by @Sinickle
it is just 30 sequences but 13 out of 30 have S:483A beyond S:346T. |
I have added a new sheet to the first one with prevalences of main indian BA.2 sublineages region by region HERE It seems that it is a team work for fast BA.2 sublineages in keeping BA.5 at the corner. This could mean they are really trasmissible as BA.5 but also that some growth advantage estimated just on India with CovSpectrum could be artificially high. |
Another sublineage appears to being growing fast in India it is a branch of the one proposed by @c19850727 in #812 |
Thanks everyone for the great work with these This is what I'm seeing, running through the clades in the order they appear in the comments from @FedeGueli above: Clade in #746 Clade in #762 BA.2.38+T7153C+S:444N+ORF1a:N3725S+orf1a:T1543I+C17373T+orf1a:T4355I+S:157S clade BA.2.38+S:417T+C21622T+S:71F+S:478R clade BA.2+K3353R+S:452M+0rf10:24L (G29628T) clade BA.2+29628T + S:452M clade BA.2.38 + S:346T+ orf1a:3763FI+C26942T clade Subclade within the clade from #812 Happy to have another look if anything changes with these. Thanks again @FedeGueli It might be easiest to close this issue and open a new issue for the BA.2.38+T7153C+S:444N+ORF1a:N3725S+orf1a:T1543I+C17373T+orf1a:T4355I+S:157S clade as this issue has a lot of information in it now |
Thank you very much @chrisruis for your very accurate work! I agree with everything stated by you above so:
Thank you again. |
Thanks @FedeGueli Sounds good |
@chrisruis i ushered the sublineage mentioned above with S:478R ( to name it quickly) it reached 108 Sequences and But what push me to re-open this issue and to designate the BA.2.38 (S:417T) sublineage with C21622T, S:69/70Del, S:S71F, S:T478R is that in the branch with S:1264L two sequences have popped up with S:452Q and S:446S beyond ORF1a:F1214I and nuc: C18744T cc @AngieHinrichs @InfrPopGen @corneliusroemer @thomaspeacock |
Probably better to reopen in a new issue. |
38 more Japanese sequences from travellers from India uploaded in the last couple of days. Collection dates 17 June to 6 July. As before, possibly a more representative sample than Indian sequencing provides. Lineage breakdown is as follows: 3 BA.2 (none from proposed lineages) |
Hi @chrisruis (and cc @corneliusroemer @AngieHinrichs @InfrPopGen ) i URGENTLY reopen this issue due to substantial changes in comparison to earlier in July: One of them is BA.2.38.1 already designated BA.2.38+S:417T+C21622T+S:69/70del, S:S71F, S:T478R proposed in #840 I suggest a fast designation of this one and its main sublineage with S:1264L
BA.2.38+T7153C+S:K147E, S:K444N, S:I692L, S:K417T+ORF1b:D51N proposed in #746 Daily updated tracker (Now upgraded with growth advantage estimated vs BA.2.75) EDIT :https://docs.google.com/spreadsheets/d/1zKF3PKaosF3OCcW54gWkyV7Spz8uWrCsYef9IHbj7FA/edit#gid=0 |
I have added #877 by @ryhisner @Sinickle Very early to say anything but still something to monitor closely cc @karyakarte |
Just posting here to mention that two more of the Indian BA.2.10 that I mentioned in #298 have turned up, and this feels like a better place to talk about it. All three (EPI_ISL_13929780, EPI_ISL_14056750, EPI_ISL_14056762) are from Maharashtra. Spike mutations W64R, 141-144del, 242-243del, G446S, F486P, R493Q, S494P, P1143L, maybe a reversion of S371F, and possibly more in S2 where all the sequences have lots of NNNs. |
Thx so much @silcn also @zach-hensel spotted these 3 ones (he is monitoring 486P) i add to the list mentioned above to monitor this possible new sublineage. it should have ORF7a:A105V too. Potential query : https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=S%3AW64R%2CS%3AG446S%2CS%3AF486P%2CS%3AS494P%2CS%3AP1143L& |
Another one for the watchlist: EPI_ISL_14166909, EPI_ISL_14167044 from West Bengal |
Thanks @silcn def something to watch closely. |
I have added to the indian sublineages sheet ( https://docs.google.com/spreadsheets/d/1zKF3PKaosF3OCcW54gWkyV7Spz8uWrCsYef9IHbj7FA/edit?pli=1#gid=1869004490) a new sheet dedicated to Clusters with multiple spike mutations mainly found and tracked by @silcn @Sinickle @ryhisner @zach-hensel @c19850727 @bitbyte2015 and others: This new sheet reports just numbers of sequences and numbers of spike mutations to keep it clean and readble at first glance. It will be ordered by number of sequences from highest to lowest. So the clusters we are monitoring actually are: <style type="text/css"></style> LineagesS:Y248S +orf1a:271S+17004T |
@FedeGueli I think "BA.2 +S:262S + S:348P + S:765L+ S:936Y (+ many others)" is the one I proposed way back in #770 which ended up not going anywhere. |
@silcn 7 more sequences of BA.2.10.1 just uploaded, from India-WB, all with spike V83A, H146Q, Q183E, V213E, G339H, R346T, L368I, V445P, G446S, V483A, F490V, S1003I like you mentioned, and also an additional spike G798D. They have this (convergent?) ORF1b:G662S as well. |
Thx @c19850727 i think it is worth proposing it on its own |
I would say that after last designations (and after the last big ba.2.38 sublineage 's issue being reopened ) this issue will be closed as completed . Thank you to the pango team for taking time to look at this deeply and to indian scientists for their super work in the labs to sequence more and more samples in thess two past months. |
((Edited 6/7)): I wrote down uncorrectly the S: 248 mutations mentioned below (now corrected) they are S:Y248S and S:Y248N , sorry everyone for this silly mistake. thx @josetteshoenma for spotting it))
Following the ongoing discussion in #773 "BA.2.75" issue
and the need expressed by @karyakarte to have BA.2 sublineages quickly designated to track them efficiently
and the important comment by @silcn:
"Regarding BA.2 lineages in India: Japan just uploaded 42 sequences from travellers from India, sampled from 27 May to 16 June, which might give a more representative sample given the differences in sequencing quantity across India. Here is the lineage breakdown according to Usher:
17 BA.2.38 (of which 1 is #809)
15 BA.2 (of which 8 are #787, 2 have S:L452M but are not BA.2.56, and 1 has S:R346T+S:L452M but is not BA.2.74)
4 BA.2.56
2 BA.2.74
1 BA.2.75
1 miscellaneous BA.1/BA.2 recombinant
1 BA.4
1 BA.5.2
I agree with the comments in that thread that there is a very strong case for designating #787.
Originally posted by @silcn in #773 (comment) "
Here i ask to designate the indian BA.2 sublineages already proposed in:
(Edited now #809 has been designated BA.2.38.1
#809 = BA.2.38 + S:444N + S:247N + S:Y248S)
#746 = BA.2.38+T7153C+S:K147E, S:K444N, S:I692L, S:417T+ORF1b:D51N
#762 = BA.2.10 S: T22N, S:L368I, S:N969R
Edited
#787 = BA.2+S:346T+S:Y248N now designated BA.2.76
Plus i ask to designate the following unproposed ones (see in the complete sheet here):
<style type="text/css"></style>
The text was updated successfully, but these errors were encountered: