Skip to content
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+M:L46F+S:F456L(318 seqs, 15 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) #2531

Open
aviczhl2 opened this issue Mar 23, 2024 · 33 comments

Comments

@aviczhl2
Copy link
Contributor

aviczhl2 commented Mar 23, 2024

From branch 26 of sars-cov-2-variants/lineage-proposals#1253

JN.1 > M:L46F (G26660T) > G4162A > S:F456L (T22928C)

GISAID query:G26660T, G4162A ,T22928C,T3565C (26 seqs)
GISAID supplementary query: G4162A,-22928,G1126A,T3565C (2 seqs, for seqs with no coverage at S:F456 but share mutation)
No. of seqs: 28(USA 4(2 from Singapore, 2 from South Korea) China 24(Hubei, Shanxi, Heilongjiang, Gansu, Henan, Hong Kong, Fujian from Taiwan, 1 from Malaysia 1 from Australia 1 from Thailand))

GISAID query for S:R346T branch: G26660T, G4162A ,T22928C,T3565C,G22599C (1 seq)

First: EPI_ISL_18872894, Hong Kong, 2024-1-27
Latest: EPI_ISL_18999287, USA from South Korea, 2024-3-12

Seems widely distributed in China and SE Asian countries.
Usher splits into two branches but the G1126A is separated by 2 Hong Kong seqs with no coverage on S:456, they shall have S:F456L too.
usher
image

@FedeGueli
Copy link
Contributor

Thank you great work

@aviczhl2
Copy link
Contributor Author

+1 Japan

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(28 seqs, 7 countries) JN.1+M:L46F+S:F456L(29 seqs, 8 countries) Mar 25, 2024
@aviczhl2
Copy link
Contributor Author

+1 UK

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(29 seqs, 8 countries) JN.1+M:L46F+S:F456L(30 seqs, 9 countries) Mar 26, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(30 seqs, 9 countries) JN.1+M:L46F+S:F456L(31 seqs, 9 countries) Mar 26, 2024
@aviczhl2
Copy link
Contributor Author

+1 Taiwan

@aviczhl2
Copy link
Contributor Author

+8 from Fujian, Anhui, Hubei and Taiwan.

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(31 seqs, 9 countries) JN.1+M:L46F+S:F456L(39 seqs, 9 countries) Mar 27, 2024
@FedeGueli
Copy link
Contributor

FedeGueli commented Mar 27, 2024

Screenshot 2024-03-27 alle 18 42 44 To me it seems really a fastg lineage, likely less than FLiRT tough. @corneliusroemer

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(39 seqs, 9 countries) JN.1+M:L46F+S:F456L(44 seqs, 9 countries) Mar 29, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(44 seqs, 9 countries) JN.1+M:L46F+S:F456L(46 seqs, 9 countries) Apr 1, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(46 seqs, 9 countries) JN.1+M:L46F+S:F456L(60 seqs, 9 countries, 18% Shanxi) Apr 2, 2024
@aviczhl2
Copy link
Contributor Author

aviczhl2 commented Apr 2, 2024

14/81=17% in the 4-1 Shanxi batch.

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(60 seqs, 9 countries, 18% Shanxi) JN.1+M:L46F+S:F456L(60 seqs, 9 countries, 17% Shanxi) Apr 2, 2024
@FedeGueli
Copy link
Contributor

ping @corneliusroemer this is fast

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(60 seqs, 9 countries, 17% Shanxi) JN.1+M:L46F+S:F456L(61 seqs, 9 countries, 17% Shanxi) Apr 3, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(61 seqs, 9 countries, 17% Shanxi) JN.1+M:L46F+S:F456L(62 seqs, 9 countries, 17% Shanxi) Apr 8, 2024
@aviczhl2
Copy link
Contributor Author

aviczhl2 commented Apr 10, 2024

+22.

16/207=8% in Hubei seqs from 2024.3.20.

@corneliusroemer

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(62 seqs, 9 countries, 17% Shanxi) JN.1+M:L46F+S:F456L(84 seqs, 9 countries, 17% Shanxi, 8% Hubei) Apr 10, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(84 seqs, 9 countries, 17% Shanxi, 8% Hubei) JN.1+M:L46F+S:F456L(85 seqs, 9 countries, 17% Shanxi, 8% Hubei) Apr 10, 2024
@aviczhl2
Copy link
Contributor Author

+1 South Korea with the same situation of Hong Kong seqs(share mut+ no coverage at 456)

@FedeGueli
Copy link
Contributor

fast growing and prevalent, ping @corneliusroemer

@aviczhl2
Copy link
Contributor Author

90, Canada

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(85 seqs, 9 countries, 17% Shanxi, 8% Hubei) JN.1+M:L46F+S:F456L(90 seqs, 10 countries, 17% Shanxi, 8% Hubei) Apr 11, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(90 seqs, 10 countries, 17% Shanxi, 8% Hubei) JN.1+M:L46F+S:F456L(94 seqs, 10 countries, 17% Shanxi, 8% Hubei) Apr 12, 2024
@FedeGueli
Copy link
Contributor

FedeGueli commented Apr 12, 2024

It got FLiRT! : EPI_ISL_19045970 @corneliusroemer this one is to watch
#2531 > ORF1a:S558F (C1938T),S:R346T (G22599C)
Query: C1938T, G22599C,G1126A

https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/subtreeAuspice1_genome_34b0_97b270.json?f_userOrOld=uploaded%20sample

Screenshot 2024-04-12 alle 20 21 12

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(94 seqs, 10 countries, 17% Shanxi, 8% Hubei) JN.1+M:L46F+S:F456L(94 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) Apr 12, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(94 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) JN.1+M:L46F+S:F456L(98 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) Apr 13, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(98 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) JN.1+M:L46F+S:F456L(100 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) Apr 16, 2024
@aviczhl2
Copy link
Contributor Author

153, New Zeland, France,

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(100 seqs, 10 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) JN.1+M:L46F+S:F456L(153 seqs, 12 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) Apr 24, 2024
@aviczhl2
Copy link
Contributor Author

aviczhl2 commented Apr 24, 2024

19/189=10% in Hubei seqs after 4-1
10/98=10% in Henan seqs after 3-20.

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(153 seqs, 12 countries, 17% Shanxi, 8% Hubei, 1 with S:R346T) JN.1+M:L46F+S:F456L(153 seqs, 12 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) Apr 24, 2024
@aviczhl2
Copy link
Contributor Author

189, Qatar,

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(153 seqs, 12 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) JN.1+M:L46F+S:F456L(189 seqs, 13 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) Apr 28, 2024
@aviczhl2
Copy link
Contributor Author

aviczhl2 commented May 1, 2024

251 seqs now

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(189 seqs, 13 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) JN.1+M:L46F+S:F456L(251 seqs, 13 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) May 1, 2024
@aviczhl2
Copy link
Contributor Author

aviczhl2 commented May 1, 2024

17/153=11% in Heilongjiang seqs after 2024-4
19/111=17% in Hubei seqs after 2024-4-15, growing fast (from 10%)

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(251 seqs, 13 countries, 17% Shanxi, 10% Hubei, 10% Henan, 1 with S:R346T) JN.1+M:L46F+S:F456L(251 seqs, 13 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) May 1, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(251 seqs, 13 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) JN.1+M:L46F+S:F456L(257 seqs, 13 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) May 1, 2024
@FedeGueli
Copy link
Contributor

17/153=11% in Heilongjiang seqs after 2024-4 19/111=17% in Hubei seqs after 2024-4-15, growing fast (from 10%)

@corneliusroemer this is faster than many Flirt lineages , already big enough to exclude founder or cluster effect, i suggest strongly an urgent designation

@aviczhl2
Copy link
Contributor Author

aviczhl2 commented May 1, 2024

17/153=11% in Heilongjiang seqs after 2024-4 19/111=17% in Hubei seqs after 2024-4-15, growing fast (from 10%)

@corneliusroemer this is faster than many Flirt lineages , already big enough to exclude founder or cluster effect, i suggest strongly an urgent designation

Maybe like EG.5.1 being faster than many early Flips.

@FedeGueli
Copy link
Contributor

17/153=11% in Heilongjiang seqs after 2024-4 19/111=17% in Hubei seqs after 2024-4-15, growing fast (from 10%)

@corneliusroemer this is faster than many Flirt lineages , already big enough to exclude founder or cluster effect, i suggest strongly an urgent designation

Maybe like EG.5.1 being faster than many early Flips.

Yeah one thing to notice is that in China FLiRT are still very low numbers so baseline is lower there allowing maybe a easier spread than , to say India or other places with higher FLiRT prevalence

@FedeGueli
Copy link
Contributor

+3 South Korea, it starts expanding outside China

@Over-There-Is
Copy link
Contributor

Over-There-Is commented May 3, 2024

Hong_Kong/HKU-240503-042/2023|EPI_ISL_19093478|2023-12-17
JN.1> G26660T> G4162A> A10066G
The earliest sequence with or without T22928C are both from Hong Kong.(Exactly EPI_ISL_18872894 and EPI_ISL_18872895 have no coverage on 22928, but the existence of T22928C could be inferenced by the following G1126A.)
I think this branch could originate in some undersampled southern provinces(e. g. Guangdong).
Or it could be from Hong Kong too, the only sequence without T22928C in Mainland is collected from Shanghai.
Rather than interior provinces which interact frequently with Guangdong, Hong Kong is more closely connected to Shanghai.

@FedeGueli
Copy link
Contributor

Hong_Kong/HKU-240503-042/2023|EPI_ISL_19093478|2023-12-17 JN.1> G26660T> G4162A> A10066G The earliest sequence with or without T22928C are both from Hong Kong.(Exactly EPI_ISL_18872894 and EPI_ISL_18872895 have no coverage on 22928, but the existence of T22928C could be inferenced by the following G1126A.) I think this branch could originates in some undersampled southern provinces(e. g. Guangdong). Or it could be from Hong Kong too, the only sequence without T22928C in Mainland is collected from Shanghai. Rather than interior provinces which interact frequently with Guangdong, Hong Kong is more closely connected to Shanghai.

thx for the analysis

@aviczhl2
Copy link
Contributor Author

aviczhl2 commented May 4, 2024

274, Netherlands, Ireland (both via GBW)

@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(257 seqs, 13 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) JN.1+M:L46F+S:F456L(274 seqs, 15 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) May 4, 2024
@aviczhl2 aviczhl2 changed the title JN.1+M:L46F+S:F456L(274 seqs, 15 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) JN.1+M:L46F+S:F456L(318 seqs, 15 countries, 17% Shanxi, 17% Hubei, 10% Henan, 11% Heilongjiang, 1 with S:R346T) May 8, 2024
@FedeGueli
Copy link
Contributor

imopressive fast , @corneliusroemer when you will be back this is one of the first to need a designation

@Over-There-Is
Copy link
Contributor

Over-There-Is commented May 11, 2024

Some sequences from Liaoning and Shanxi got 4162 reverted, but I don't think they're true

@Over-There-Is
Copy link
Contributor

Multiple cities, Liaoning 05-10 13/101
Jincheng, Shanxi 05-07 6/51

@Over-There-Is
Copy link
Contributor

*Some sequences have neither G1126A nor G4162A. They should be investigated further.

@FedeGueli
Copy link
Contributor

FedeGueli commented May 11, 2024

*Some sequences have neither G1126A nor G4162A. They should be investigated further.

new query G26660T,T22928C,T3565C should catch all of them , count 343

G1162A is not defining of this:
Screenshot 2024-05-11 alle 15 52 56
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_test_334cb_f77170.json?c=gt-nuc_1126&f_userOrOld=uploaded%20sample&gmax=2126&gmin=126&label=id:node_6996795

@FedeGueli
Copy link
Contributor

349

@Over-There-Is
Copy link
Contributor

Over-There-Is commented May 14, 2024

*Some sequences have neither G1126A nor G4162A. They should be investigated further.

new query G26660T,T22928C,T3565C should catch all of them , count 343

G1162A is not defining of this: Screenshot 2024-05-11 alle 15 52 56 https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_test_334cb_f77170.json?c=gt-nuc_1126&f_userOrOld=uploaded%20sample&gmax=2126&gmin=126&label=id:node_6996795

But some sequences have reversions on 4162 and 3565, and they could still be identified by G1126A.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants