-
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
Multiple branches of BA.2.86* with S:S31del 2 Unproposed branches as of 8/23 #1502
Comments
@ryhisner thinks it could create a new Glycan at S:N30. |
It's growth is 25%. And it adds 60%(total 101%) to S:R346T variants, super fast combo, as fast as S:F456L does. @AngieHinrichs, may be the first time usher facing a real problem, that a super-fast convergent deletion appears. |
Very good job @aviczhl2 thank you. |
Br 5 and 7 look fast. |
Br 5 7 9 new sequences count updated. |
Updated the existing branches. (Tracking comment) CLOSED There should be more:
|
updated. this one and main proposal count i would propose Branch 5 KP.1.1 it seems growing quite fast. |
there is an interesting DeFViRT singlet from #2538: Now July 4 is MA.1 (edited) |
Br.7 is JN.1.48 |
Br.12 now goes to 8 |
|
From #1089: FIrst ever DelTRIO
|
@Sinickle found yesterday the first DelKP.3 : |
sequence count updated for unproposed lineages , also countries added . Branch 9 seems expanding in Brazil ( i didnt check tough if it the same lineage or query needs to be updated) @aviczhl2 Update: Br. 9 seems not monophyletic: https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_test_d0f1_cb1a30.json?f_userOrOld=uploaded%20sample&label=id:node_7063835 The Brazilian branch seems an independent having JN.1.4> > S:346T, Orf8:E106Q but it is splitted on Usher. So i suggest C774T,T18453C, -28201, del21653_21655,-G28209C as new query for Br.9 |
@aviczhl2 analysis done |
thank you |
@FedeGueli Branch 34 isn't fully LP.2. So actually shall be two separate branches. 1: KP.1.1+S:S71Y,S31del @corneliusroemer what do you think of the possibility of branch 1 being a recombinant of LP.2 and KP*? I've altered the query for branch 34 to exclude LP.2. |
Branch 31 is now 5, last one from France, still no sample from August if one more from August will come please propose it. |
Good catch! so i tend to think it is a recombinant losing Orf1b:T2376I and 4999T |
Branch 31 becomes 10, +5 from South Korea. No, only the GBW one of the branch has S:S31del, others seem separated prior to that with only S:A163V Branch 34 Now 32 seqs. Continue being detected in South Korea and Malaysia in August, |
i didnt get what you mean |
Ah got it so add Dead label to it, i was monitoring it in the other issue and it has been 2 from a long time, no neeed to track 163V here no? |
Please propose Br.34 please |
Yeah pls make a separate issue if you want. |
Pls do it , if it is going! |
Branch 21 detected in France and Moldova. |
Branch 21 detected in USA local and imported case from UAE. |
I'll propose branch 21 and close this multi-lineage issue. For future S:S31- branches please make separate issues. |
Br.31 reached 16 with a sample from Laos maybe worth extracting it? |
nevermind it is the infiltrated here withoiut 31del sorry. |
There is a KP.4.1 branch + S:S31del that i am going to propose, it is quite an old one but got 5/63 samples after Sept 1 from three different continents. cc @xz-keg |
I think that branch is just separated by usher recently, previously likely hidden in some artifact flip-flop branches. |
Yeah likely |
KP.3.2 defluqe branch 32 went to 11 with 4 samples from September 2 Sweden, 2 Spain GBW (1 pooled) |
There is an untracked KP.1.1 s:s31del branch still circulating in a mini saltation branch with S:175L and S:K478I in Sweden KP.1.1 > C3457T > C3695T, Orf1a: E2089D (G6532T), A14457G, C18981T > S:S31del (del21653-55) > if it will grow further i will make a separate issue for the mini saltation branch |
It seems that there's many S:S31del lineages emerge now. This deletion was in previous variants but rather rare, however under BA.2.86* it seems much frequent.
A very interesting fact is that this deletion seems tied extensively to S:R346T.
GISAID query: del21653_21655,del22193_22195
Tasks
Also various singlets, they may be actually gathered under JN.1+S:S31del, however usher doesn't show that branch so hard to tell.
The text was updated successfully, but these errors were encountered: