-
Notifications
You must be signed in to change notification settings - Fork 97
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
BA.2+22792T sublineage with S:I68T circulating in Belgium (6%) -1373 seqs globally #565
Comments
These S:68T are tricky, they appear in so many places. So all individual lineages are still quite small despite S:69T being in 6% of Belgian sequences! |
yes @corneliusroemer and the same happens for orf8:65V : many lineages but all of them small but the Papua new guinea one recently designated |
I'd say we should designate this without the ORF8:65V mutation. It's probably not relevant here. S:68T appeared on the European BA.2 + 22792T branch with no other private mutation present at the time of mutation. That's now grown to 7% in Belgium - so quite possible this mutation arose in Belgium and has spread slowly from there. In total 1400 sequences by now. |
Yes @corneliusroemer i agree totally with you. at the beginning i was afraid that just S:I68T could be confounded by other unrelated clades bringing this mutation. so it was easier to monitor the double mutation. But now orf8:65V is just 1/3 of S:68T sequences in Belgium. i ll change the title of this proposal consequently. |
Added new lineage BA.2.36 from #565 with 976 new sequence designations, and 109 updated designations
Thanks for submitting. We've added lineage BA.2.36 with 976 newly designated sequences, and 109 updated designations. Defining mutation(s) T21765C (S:I68T). |
|
The designated sequences seem to be messy - no super majority actually has |
is it my fault @corneliusroemer ? can i help in some way? i can re extract a more stringent sequence list if needed |
@corneliusroemer i checked the query i used to extract the sequence list and so ething weird happens: On covspectrum Pangolin recognizes that as BA.2.36 (99%) whilr nextclade missassigned all of them to BA.2. and S:I68T and 22792T were there in 100% of them |
Follow up from #524 .
I want to propose here a sublineage of BA.2 carrying S:I68T and Orf8:A65V.
As shown in a comment in issue 524 recently S:I68T (spotted by @olias12061976) and orf8:A65V (spotted by @bikuduh) appeared indepently and separately in several BA.2 sublineages .
One of them carries both these two emerging mutations and it is circulating in Germany Belgium Denmark Israel and have been sequenced in USA and UK too.
Here the list of 373 sequences :
contributors (87).csv
Its share is increasing vs BA.2 baseline
And it is showing an apparent growth advantage ranging from 15% in Israel to 70% in Denmark
Interestingly 83% of this sublineage is missassigned to BA.2.9 while lacking or3a:H78Y defining BA.2.9 mutation
https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=S%3AI68T%2COrf8%3AA65V&
Usher tree (by @bikuduh)
The text was updated successfully, but these errors were encountered: