Skip to content

Elevate XBB.1.16 as new clade 23B#1059

Merged
corneliusroemer merged 2 commits intomasterfrom
xbb-1-16-as-23B
Apr 17, 2023
Merged

Elevate XBB.1.16 as new clade 23B#1059
corneliusroemer merged 2 commits intomasterfrom
xbb-1-16-as-23B

Conversation

@corneliusroemer
Copy link
Copy Markdown
Member

@corneliusroemer corneliusroemer commented Apr 11, 2023

Elevation criteria

In India, XBB.1.16 has reached a share of around 75% in samples collected mid March.

In all Asian sequences in GISAID at time of writing, XBB.1.16 represents around 10% of all sequences collected mid March.

A simple logistical growth model shows an absolute daily growth advantage of around 9% in all of Asia.

The relative growth against all of XBB* is around 5% in India.

Similar advantages are also apparent in the US.

XBB.1.16 hence clearly satisfies criterion 4 of the most recent Nextstrain clade naming criteria ("A clade shows consistent >0.05 per day growth in frequency where it’s circulating and has reached >5% regional frequency", see https://next.nextstrain.org/blog/2022-04-29-SARS-CoV-2-clade-naming-2022).

Also the additional requirement of "multiple mutations in S1 or particular mutations of known biological relevance." are satisfied, as compared to parental 22F (XBB), XBB.1.16 has 3 S1 mutations (180V, 478R, 486P) of which 2 are in the receptor binding domain and of known biological relevance (478R, 486P). While is already present in clade 23A (XBB.1.5), XBB.1.16 has evolved this substitution independently. What makes XBB.1.16 distinct is the additional substitution 478R.

Share of XBB.1.16 vs other clades over time in select countries (logit scale):
image

Absolute numbers of cases (to be taken with grain of salt due to changing testing) in select countries showing XBB.1.16 driving a wave in India (linear scale):
image

Log plot of absolute number of cases in select countries:
image

These were all created by @trvrb using https://github.com/blab/rt-from-frequency-dynamics/tree/master/results/omicron-xbb116

Here are some further plots of relative growth advantages of XBB.1.16 vs XBB*+486P (comprising all XBB.1.5-like lineages) via covSpectrum, showing that XBB.1.16 is not just another XBB.1.5 but appears to outcompete it, at least in those countries: (take exact numbers with big grain of salt, but trends and significance is clear)
image
from: https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?aaMutations=S%3A486P&nextcladePangoLineage=XBB*&variantQuery1=nextcladePangoLineage%3AXBB.1.16*&analysisMode=CompareToBaseline&

Checklist, from Slack:

  • NCoV file updates
    • defaults/clade_emergence_dates.tsv
    • defaults/clade_hierarchy.tsv
    • defaults/clades.tsv
    • defaults/clades_nextstrain.tsv
    • defaults/color_ordering.tsv
    • defaults/emerging_lineages.tsv
    • changelog
  • Explain in PR why we are elevating
  • Start test build: will be at ".../open/23B/global/6m" etc, first builds should be there by 11am UTC
  • Check test build
  • Pass PR review
  • Merge PR
  • Update clade diagram figure
  • Add new variant (with new name) to Nextclade dataset
  • Trigger full runs on GISAID & Genbank once Nextclade updated
    • Add touch files
    • Ingest
    • Deactivate auto-triggered runs
    • Reactivate auto-triggered runs once ingest complete
  • Update covariants
  • Draft tweet
  • Send tweet

@corneliusroemer corneliusroemer merged commit 6d76876 into master Apr 17, 2023
@corneliusroemer corneliusroemer deleted the xbb-1-16-as-23B branch April 17, 2023 20:17
joverlee521 added a commit to nextstrain/forecasts-ncov that referenced this pull request Apr 17, 2023
Adds new variant elevated in nextstrain/ncov#1059

Includes adding the variant to model configs.
Updates the hardcoded color and display name maps for the viz app.
Changed 21A to a purple color (#7725c6) and shifted the colors for all
other variants so that the latest variant is the bright red color (#FF322C).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

2 participants