-
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 JN.1* branches with S:F456X : 4 Ongoing Unproposed Branches as 7/25 #1253
Comments
please name the lineages Branch 1 branch 2 branch 3 etc |
JN.1+Orf1a:T2283I,S:F456L,V1104L Query: C7113T,T22928C,T3565C, India This one is detected in another India state and becomes a branch. |
agree already in my tracking list it seems v interesting. |
They are placed in different branches on usher but that's due to artefacts of India-KA seqs around S:16. KA seqs seem to artefact the ins16MPLF to some other things on all its JN.1* seqs. |
I managed to get a tree and a query for the parental lineage of Branch 4 with S:V1104L: Query: G24872T, G17334T,C897A finds 11 Samples: EPI_ISL_18682687 (Recomb), EPI_ISL_18683064, EPI_ISL_18694660, |
i think i ll propose (or you as you want ) the parental branch so Branch 4 could be defined as #XYZ + 456L, what do you think? |
Yes sure. |
|
branch 3 goes to 11 |
Add doublet 1 from USA. There seems to be also S:F456V and S:F456I branches. Include them for branch 5 and singlet 7. |
1/10: Branch 4 Goes to 6 and spread to UK |
@aviczhl2 i would ask you to propose it together with the parental in the main page (closing my side proposal) , so @corneliusroemer could track it too . If you can keep it updated also here it would be great. |
5 in India and 1 in UK actually. Discovered in 2 India states. You can propose that as your proposal is more focused? If you want me to propose that's also fine. |
as you prefer! you discovered the whole thing! but if u have no time i will! u can copy paste it and then add the analysis of the 456 branch |
1/12: |
branch 115 now 5 with last samples coming from Israel and Netherlands. @aviczhl2 please propose , it seems relevant, too much to be buried in a multiple lineages issue. |
Branch 15,51,57,62 and 110 might be dying off, please close it (denote it with [*] instead of [P]) |
done |
Branch 21,36,41,48,58,67 and 73 might be dying off, please close it now (denote it with [*] instead of [P]) |
Branch 8 grows to 26, reopen. |
I think this one can be closed now. Almost everything now has S:456X. The proportion of S:456F seqs is around 1% and 99% of the seqs belong to 456X lineages. For new 456X lineages pls make separate issues @FedeGueli @ryhisner |
Branch 110 is 49 now, with many recent samples @FedeGueli |
I think we shall get rid of those DailyCovidCases proposals that are never updated correctly, and re-propose some of the branches if they are still there. @FedeGueli |
it should be 46 with -G17334T,-T3913A,-G1126A,C19374T, T22928C, T3565C,-C1762A,-17334,-7113 , yeah agree with multiple branches opened and closed it has been a chaos, maybe next week i will have some time to check all the branches and verify if we lost something on the road. in the meanwhile propose BR.110 here on this repo(if still monophyletic) |
BR.115 Designated JN.1.16.5 via cov-lineages/pango-designation@56fe08a |
JN.1.4 + 456L + 475V from China: |
This is 54 seqs now, most come from July, and a South Korean branch gets additional S:S60P, S:T572I and S680P |
re propose it please |
i think the query has to be adjusted again also the tree is not super clear with two branches with 456l: |
@aviczhl2 i suggest to propose only the fast growing S:S60P ( also convergent with XDV.1.1) starting from S:S60P and orf1a:Y1734H (PLPRO_Y171H) |
Yeah I was about to propose that branch but some Chinese July seqs seem on the lower branch. |
SO lets start from C9988T, those chinese cluster seems quite interesting |
Flirt branch 84 is 35 now, a Lithuanian imported case is also detected by US |
Please @aviczhl2 (only you) extract it from here to this repo, maybe worth tracking for a bit being quite widespread in Russia ( so we will tag with undersampled area label and let it open for a while) |
Last upload from 8-12 and last Russian upload at 7-30. Waiting for the next Russian upload to decide. |
Branch 116 designated LZ.2 please update the title |
Branch 8,110,114,117,118,119 are dying off, please denote it with [*] |
Thx but this is closed and dusted! |
It seems that S:F456L is very convergent in JN.1 now. (last complete update June 19)
28 seqs, UK, Canada, Denmark,Netherlands,Singapore, Sweden, USA,Luxembourg
JN.1.4+C22450T+Orf1a:T2274I, S:F456L, Query: C22450T, T22928C, T18453C, 5 seqs, South Korea
JN.1+C14178T+S:F456L,Q613H,Orf1a:V2783F, Query: C14178T,T3565C,T22928C,G23401T, 4 seqs, USA
Doublets and Singlets no longer tracking. Only track >=3 branches, or branches with seqs from multiple countries now.
The text was updated successfully, but these errors were encountered: