-
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
JN.1+S:V1104L emerging in India(Designated JN.1.11, 16 and 5 countries with Orf1a:T2283I and S:F456L ) #2446
Comments
Also found this one - it's a bit tricky to designate due to the artefacts, there's now an Israeli sequence as well though with 456L And two Texas seqs without 456L:
|
I've designated via the non-Indian sequences with 1104L for now as JN.1.11, the 456L would be a sublineage in the future |
Yep, it's currently placed on a messy reversion branch within JN.1.1 instead of JN.1. When the 2024-01-11 build finishes I will do some pruning & re-optimization on the tree, and then hopefully in tomorrow's 2024-01-12 build JN.1.11 will be in the right place. |
The S:F456L branch is 10 now. |
456L 15 now |
Countries for F456L branch: |
@corneliusroemer could you reopen this one to track properly the 456L branch please? |
JN.11> A12889G> T3055C> T22926C or JN.11.1> T3055C? |
From sars-cov-2-variants/lineage-proposals#1253 branch 4 and sars-cov-2-variants/lineage-proposals#1262
JN.1+G17334T,G24872T(S:V1104L)
GISAID query: G24872T, G17334T,C28958A
No. of seqs: 21(India 20 UK 1)
First: EPI_ISL_18694669, India-GJ, 2023-12-7
Latest: EPI_ISL_18725672, India-MH, 2024-1-1
20/790=2.5% in India seqs from 2023-12. From GJ, KA and MH.
+C7113T,T22928C(Orf1a:T2283I,S:F456L)
GISAID query: C7113T,T22928C,T3565C
No. of seqs: 6(India 5 UK 1)
Note that due to artefacts usher places those seqs on different branches. Some with S:V483G artefact are placed together,
some with artefacts around S:16 are placed together, and seqs with other artefacts are placed in other places.
@AngieHinrichs
current usher
The text was updated successfully, but these errors were encountered: