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

Designate clades 24A (JN.1) and 24B (JN.1.11.1) #1103

Merged
merged 2 commits into from
Apr 5, 2024

Conversation

corneliusroemer
Copy link
Member

@corneliusroemer corneliusroemer commented Mar 14, 2024

With this PR, we are designating 2 new Nextstrain clades:

  • 24A = JN.1 (= BA.2.86.1.1)
  • 24B = JN.1.11.1 (=BA.2.86.1.1.11.1)

24A = JN.1 (= BA.2.86.1.1)

24A = JN.1 (= BA.2.86.1.1) is a sublineage of 23I = BA.2.86 with extra spike receptor binding domain mutation L455S.

It descends from BA.2.86.1, the BA.2.86 lineage that spread most successfully, globally, with extra AA substitution ORF1a:K1973R.

24A was first sequenced in Iceland (collection date 2023-08-29, submission date to GISAID 2023-09-20) and became dominant in Iceland by the end of October 2023. The first large country where 24A was dominant was France, by the end of November 2023. JN.1 reached dominance in the majority of countries with active surveillance by the end of 2024.

24A satisfies clade criteria 2, 3 and 4: "A clade reaches >20% regional frequency (criterion 3 for Europe), >30% global frequency (criterion 2) for 2 or more months" and "A clade shows consistent >0.05 per day growth in frequency where it’s circulating and has reached >5% regional frequency" (criterion 4).

Below is a 6m global tree showing 24A (JN.1) in red:

image https://nextstrain.org/ncov/gisaid/global/6m?branchLabel=emerging_lineage&c=emerging_lineage f8a6">

24B = JN.1.11.1 (=BA.2.86.1.1.11.1) = KP

24B = JN.1.11.1 (=BA.2.86.1.1.11.1) is a sublineage of 24A = JN.1 with extra spike receptor binding domain substitutions S:F456L and S2 substitution S:V1104L. It also has synonymous nuc substitution G17334T and non-synonymous C7113T=ORF1a:T2283I, a mutation that has appeared multiple times during the pandemic, e.g. as defining in C.39, XDE and making up around 10% of EG.5.1.4.

JN.1.11.1 is aliased to KP, so all sublineages start with KP

The first 24B sequence was sequenced and released in India (Karnataka) in December 2023 (collection date 2023-12, submission date 2023-12-24) by the National Centre for Biological Sciences, TIFR - Rockefeller Foundation. India shared the first 4 known sequences and also sequenced many ancestral JN.1.11.

US traveller surveillance suggests JN.1.11.1 is common in Asia, particularly in India, but with imports from a variety of countries stretching from Turkey, via Qatar to Japan. Around 20% of recent US traveler sequences (collection date early March) were from JN.1.11.1. In Singapore, in sequences collected since March 1, 16 out of 67 JN.1* (20-25%) were JN.1.11.1.

Due to reducing global surveillance, and submission delays of up to 2 months, it is difficult to estimate the overall growth advantage of JN.1.11.1 (for instance, the most recent Indian sequence on GISAID was collected on Feb 5, more than 7 weeks ago).

S:R346T has appeared at least 2 times independently in JN.1.11.1 and seems to confer an additional growth advantage that contributes to the overall fast rise of JN.1.11.1

24B satisfies clade criterion 4: "A clade shows consistent >0.05 per day growth in frequency where it’s circulating and has reached >5% regional frequency" as it is clearly above 5% frequency in South Asia with a growth advantage significantly above 5% per day.

Below is a 1m global tree showing 24B (JN.1.11.1) in red:

image

Doubling time of sequences in GISAID, by submission date of JN.1.11.1 + S:R346T

N Submission Date of Nth sequence Days between doublings
1 2024-01-20  
2 2024-02-20 0
4 2024-02-21 1
8 2024-02-26 4
16 2024-03-01 3
32 2024-03-06 6
64 2024-03-12 6
128 2024-03-18 6
256 2024-03-27 9
(399) 2024-04-04 (8)

This is the growth of JN.1.11.1* per https://nextstrain.github.io/forecasts-ncov/

image

JN.1.11.1 is clearly fitter than JN.1

image

There are other JN.1* + 346T + 456L but none are as frequent globally as JN.1.11.1 is.

Pre-merge checklist

Post merge checklist

  • Add new variant (with new name) to Nextclade dataset color_ordering.tsv
  • Update clade diagram figure
  • Trigger full runs on GISAID & Genbank once Nextclade updated
  • Tweet about new variant

@AngieHinrichs
Copy link

Changes look good but the PR title should say 24A instead of 23A. 🙂

@corneliusroemer corneliusroemer changed the title Designate clade 23A (JN.1) Designate clade 24A (JN.1) Mar 14, 2024
@corneliusroemer
Copy link
Member Author

Changes look good but the PR title should say 24A instead of 23A. 🙂

Done, thanks @AngieHinrichs! I've made that mistake about 5 times already, I caught it 3 times 🙃

@corneliusroemer corneliusroemer marked this pull request as ready for review April 4, 2024 07:01
@corneliusroemer corneliusroemer requested a review from rneher April 4, 2024 07:09
@corneliusroemer corneliusroemer changed the title Designate clade 24A (JN.1) Designate clades 24A (JN.1) and 24B (JN.1.11.1) Apr 4, 2024
@corneliusroemer corneliusroemer merged commit 1f7265a into master Apr 5, 2024
17 checks passed
@corneliusroemer corneliusroemer deleted the clades-2024-03 branch April 5, 2024 20:55
joverlee521 added a commit to nextstrain/forecasts-ncov that referenced this pull request Apr 8, 2024
Following up on new Nextstrain clades added in
nextstrain/ncov#1103

Updated the clade colors, similar to what was done in
afbf2fb. Copied and pasted colors from
https://github.com/nextstrain/auspice/blob/cff84b3cbf13212a91c537a0b63e824682b7ebc0/src/util/globals.js#L104C3-L104C136
diff --git a/config/config.yaml b/config/config.yaml
index d109d56..634929e 100644
--- a/config/config.yaml
+++ b/config/config.yaml
@@ -93,46 +93,54 @@ mlr_config: "config/mlr-config.yaml"
 # * Lineages which are not a descendant of a clade-defining lineage will be
 #   grouped as 'other'
 clade_definitions:
+  - clade: "24B"
+    display_name: "24B (JN.1.11.1)"
+    defining_lineage: "JN.1.11.1"
+    color: '#DC2F24'
+  - clade: "24A"
+    display_name: "24A (JN.1)"
+    defining_lineage: "JN.1"
+    color: '#E4632E'
   - clade: "23I"
     display_name: "23I (BA.2.86)"
     defining_lineage: "BA.2.86"
-    color: '#DC2F24'
+    color: '#E69136'
   - clade: "23H"
     display_name: "23H (HK.3)"
     defining_lineage: "HK.3"
-    color: '#E56C2F'
+    color: '#D9AD3D'
   - clade: "23G"
     display_name: "23G (XBB.1.5.70)"
     defining_lineage: "XBB.1.5.70"
-    color: '#E39B39'
+    color: '#C1BA47'
   - clade: "23F"
     display_name: "23F (EG.5.1)"
     defining_lineage: "EG.5.1"
-    color: '#CEB541'
+    color: '#A2BE57'
   - clade: "23E"
     display_name: "23E (XBB.2.3)"
     defining_lineage: "XBB.2.3"
-    color: '#ADBD51'
+    color: '#83BA70'
   - clade: "23D"
     display_name: "23D (XBB.1.9)"
     defining_lineage: "XBB.1.9"
-    color: '#88BB6C'
+    color: '#69B091'
   - clade: "23C"
     display_name: "23C (CH.1.1)"
     defining_lineage: "CH.1.1"
-    color: '#69B091'
+    color: '#549DB2'
   - clade: "23B"
     display_name: "23B (XBB.1.16)"
     defining_lineage: "XBB.1.16"
-    color: '#5199B7'
+    color: '#4580CA'
   - clade: "22F"
     display_name: "22F (XBB)"
     defining_lineage: "XBB"
-    color: '#4042C7'
+    color: '#3E58CF'
   - clade: "23A"
     display_name: "23A (XBB.1.5)"
     defining_lineage: "XBB.1.5"
-    color: '#4274CE'
+    color: '#462EB9'
   - clade: "other"
     display_name: "other"
     defining_lineage: False
joverlee521 added a commit to nextstrain/forecasts-ncov that referenced this pull request Apr 8, 2024
Following up on new Nextstrain clades added in
nextstrain/ncov#1103

Updated the clade colors, similar to what was done in
afbf2fb. Copied and pasted colors from
https://github.com/nextstrain/auspice/blob/cff84b3cbf13212a91c537a0b63e824682b7ebc0/src/util/globals.js#L104C3-L104C136
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

Successfully merging this pull request may close these issues.

2 participants