-
Notifications
You must be signed in to change notification settings - Fork 3
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
XEC/XEK spike diversity issue (Updated as of Dec 22) #2088
Comments
Very good idea, i will try to help. do u prefer direct editing or highlighting in the comments? I would require also that the lineage has to be sampled at least once in September ( or last 30 days) to avoid dead ends |
Sure, you can do direct editing. |
Branch X: XEC+Orf1a:A599T+S:S680F (furin), 5seqs (1xFrance, 1xCanada, 3xUS). Arose 2x independently (all US sequences are separated on the Orf1a:T2274I subbranch = XEC.9, edited). All seqs less than 1 month old. Query: G2060A, C23601T |
Branch X: XEC+Orf1a:A599T+S:E1202Q, 2 seqs, France + Ireland. Query: G2060A,C11020T,G25166C |
Br.7 went to 8 with three GBW samples from Peru' (2 patients) |
Branch X: XEC+S:W152R (defining for Centaurus) arose convergently: Branch X via T22016A (1xNL, 1xFR). Branch 11 via T22016C (1xIR, 1xUSA). All seqs sampled in September |
Branch X: XEC+S:T678I (C23595T), furin-adjacent. 4xCAN, 2xFR, 2xUSA. Convergent: one on the Orf1a:I1367L, the rest on the Orf1a:A599T polytomy. All seqs sampled in September |
Please separate these branches and ensure every branch is monoplyetic. |
Branch X: XEC+S:P1263L(C25350T), same site as branch 13. 1xSW,1xPL. |
Please check with usher before proposing. They seem to be on different usher branches. If they are on different usher branches it is likely they emerge separately and shouldn't be treated as one. Unless you provide reason (artifact, usher-flip flop, convergent other mutations like branch 7, etc. ) to merge them. |
IMO, at present the relatively low number of XEC seqs makes it hard to correctly assess the phylogeny, the resolution is still insufficient. The total XEC Usher tree still places most seqs on polytomy. |
@aviczhl2 i think soon we will be force to raise the parameters to three places and 10 seqs, i tell this because in my previous experience with spike diversity issues it rapidly becomes very mess or too long with the opposite effect to risk hiding something fast instead of highlighting it. It is not yet the moment but we shopuld think about it. |
Branch X: XEC+Orf1a:A599T+S:K182N. 3xNL, 1xENG, 1xCanary Islands (with additional S:M153I). Monophyletic, query: C829T, A22108T |
Not a Branch but worth tracking: XEC + Orf1a:A599T+ S:A475V |
Solved 5 now from Br.8 also from Germany it looks interesting
|
Branch X: XEC+Orf1a:A599T+S:G72R. 5 seqs, 5 countries: Denmark, Netherlands, France (with S:K113R), Canada, GBW from Mexico. Query: G2060A, G21776A,T3565C (edited) |
i ve added T3565C to exclude old samples. |
You can directly edit the task list. But be cautious on cvejris proposals that may not be monophyletic. |
yeah i m a bit confused about the branch numbering . @cvejris i suggest just to add the lineage you find without a branch number |
XEC+ Orf1a:A599T + S:P561H (C23244A) |
Important (likely): XEC got S:I68F (by Gisiad correctly) ( read as S:-70F by USher, Covspectrum and Nextclade ) : Now added as branch 13 Ping @corneliusroemer here something to watch |
Jumped to 7 with a batch from France, 2 different provinces |
+3 GBW from Turkey, you can propose it to main. |
the XEC+475V + orf3a:S60F + Orf6:L52F Ontario cluster grew to 14 and recent samples. One to watch if it manages to exit the cluster. (Q: C6582T, T19230C, C22522T,) |
Br 17 went to 34 |
A former Scottish cluster now found also in Denmark with S:S514F should i add it? cc @xz-keg |
yeah pls |
Br.56 now |
Br.25 , formerly thought dead now jumped to 15 with a batch from Japan , 4 of the new samples have S:P384S that is predicted by J Bloom to be a hotspot for immuno escape., |
also NDPFL137-141M |
All 10 Japanese sequences of Branch 25 have C21997T. |
yeah i saw that and the deletion even a bit messy on nextclade, i will re fromulate the br.25 to include all the nodes (it is hard to specify for sub brannches in multiple lineages proposalS) thx for checking |
to me it is |
branch 17 is now 35 @FedeGueli I'll propose it? |
branch 47 designated XEK.4 via cov-lineages/pango-designation@7cb9d21 branch 54 designated XEC.16 via cov-lineages/pango-designation@4256d9b |
There is an interesting branch of XEC that in its least branch evolved S:T33K and S:141-144del: For now just a cluster. |
Br.53 (444R) one more from NZL (new) |
Add branch 57 (XEC.2+R765L) raise threshold for 2 place branches to 10 seqs. (still no threshold if detected in 3 different places) |
Br.55 appears to be fast.- everything just updated |
Added several -s to Br.29 (681H) |
C8146T,T2803C,G25249T M1229I CA-ON |
XEC.2.2 + T572I T1104C, T9508C, C23277T 3 UK, Ireland |
Another XEC.8+S:A688V, C23625T,C28603T, not on T27995C branch |
added as branch 59 |
branch 55 is 32 now. |
added as branch 60. |
It seems that there is, and will be a lot of spike diversity in XEC. Better gather them in one issue.
Only count for branches with more than 10 seqs from 2 places, or from 3 or more places (NEW)
GPT Model trained on August data(seqs before XEC appears) predicts 4 spike mutations for XEC on top potential mutation list: S:T572I, S:R346T, S:N185D, S:A688V.
Tasks
The text was updated successfully, but these errors were encountered: