-
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:F456L + S:V407i (37 seqs, Spain) #2584
Comments
it doesn't seem slow. Gisaid nuc query: T17556C, G22781A |
This is not sub-branch of JN.1.16, but rather sub-branch of branch 34 in sars-cov-2-variants/lineage-proposals#1253 |
Yes you are right, @Sinickle please broad the proposal with that so jn.1+456L (as in # 1253) crediting @aviczhl2 and then the sublineage of interest with S:V407I |
Wow it went to 28! @corneliusroemer ping! |
I don't think it's clear that this is a sublineage of JN.1 rather than JN.1.16? |
More likely from A9085G branch because S:F456L is much more convergent than A9085G, it is unlikely for A9085G to appear multiple times and form sizeable branches, but very likely for T22928C to appear both under JN.1 and JN.1+A9085G . |
@Sinickle i agree with @aviczhl2 Jn.1.16 ( as Jn.1.18 ) are not monophyletic lineages but instead big collectors of early convergent branches with 456L (or 346T for JN.1.18) In fact sometime we find in those lineages misplaced branches that are instead also outside of it . So if this has A9058G and A9085G exists outside S:f456L, it is 99% it comes before |
Even though S:F456L is more convergent, "vanilla" JN.1.16 is still much larger than JN.1 + A9085G. So that aspect would shift it in favor of JN.1.16. I tried to trim off some of the branches to get a query for "vanilla" JN.1 + A9085G, and for vanilla JN.1.16, to see how large each was. JN.1.16 is still the larger one, but if we limit it to Spain and limit it to before the first sequence of the proposed lineage appeared, then JN.1.16 has 11 in Spain, and JN.1 has 7 in Spain, which isn't enough of a size difference to make up for the difference in the convergent nature of S:F456L. So I agree that JN.1 is more likely overall. Thanks! |
i found some news of an apparent increase in cases in Galicia, we should monitor this one if related or not to that> https://x.com/Miguel_Leiva_/status/1789347080718123008 Prevalence of this in Galicia seems to be as high as 30% especially in some areas of it. |
32 +2 Galicia (Coruna) |
There is now one of this proposed sublineage collected May 5 from Toledo Spain. |
Designated JN.1.54.1 |
Designated JN.1.54.1 via d4897da |
This proposed lineage was first found by @aviczhl2 in this issue.
GISAID Query: T17556C, G22781A
First Seq: EPI_ISL_18963344, Feb 11 Spain / Andalusia / Almeria
Prevalence:
15/75 sequences collected from Galicia Spain March 3-April 5.
18/79 of sequences in Galicia Spain collected since April 6.
Mutations: JN.1 + A9085G -> S:F456L + S:V407i + T17556C. Then all except for the first sequence have T6552C and C12400T.
It's also possible that this is instead JN.16 + A9085G + S:V407i + T17556C
Tree
Discussion:
Proposing this one due to its high prevalence in two different regions of Galicia Spain, which has accumulated across 3 uploads. Additionally this proposed sublineage is in Asturias Spain in addition to Andalusia and Galicia. Since the S:V407i mutation is accompanied by T17556C, it is pretty distinct.
The text was updated successfully, but these errors were encountered: