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

Elevate Pango lineage BA.2.75 to Nextstrain clade 22D #984

Merged
merged 2 commits into from
Jul 22, 2022

Conversation

trvrb
Copy link
Member

@trvrb trvrb commented Jul 20, 2022

This elevates the Pango lineage BA.2.75 to Nextstrain clade 22D with the label 22D (Omicron) as impactful Omicron sub-lineages BA.2, BA.4, BA.5, etc... are still labelled as Omicron by the WHO.

Critically, BA.2.75 has been increasing in frequency rapidly in India with a consistent logistic growth rate of 0.13 per day, compared to a logistic growth rate of BA.5 of 0.01 per day.

omicron-ba275_logistic-growth-transformed-axis-BA5-BA275

BA.2.75 was at 15% frequency directly estimated from GISAID data at the beginning of July. This increase of 0.13 per day is comparable to observed increase of BA.5 in the US and the UK in May.

Observing this similar trajectory of BA.2.75 in India as observed for BA.5 in multiple geographies strongly suggests that this will be a globally competitive clade, especially as we're seeing BA.2.75 directly outcompete BA.5 in India.

Additionally, there are nine spike substitutions observed in BA.2.75, including reversion of 493 to wild type, which is greater than the three substitutions observed in BA.4/5.

ncov_variants_shared_mutations_ba5_ba275

These mutations include G446S which is shown to escape from existing immunity to BA.2 viruses in DMS assays.

Previous Omicron-derived clades 22A (Pango lineage BA.4), 22B (lineage BA.5) and 22C (lineage BA.2.12.1) have driven sizable epidemics across the globe due to a combination of antigenic drift and increased intrinsic transmissibility.

Our primary rationale for labeling Nextstrain clades remains one of circulation and being able to discuss circulating viruses that are driving epidemics.

Our existing 4 point rationale includes:

  1. A clade shows consistent >0.05 per day growth in frequency where it’s circulating and has reached >5% regional frequency

as a mechanism to identify a clade early on that is expected to circulate widely. However, this threshold has not been reached for BA.2.75 due to how we calculate "regional" frequency, in this case, frequency in Asia. Our regional frequency estimates subsample viruses within a region equally across countries within a region. However, India is a huge country and observing 15% frequency in India is perhaps 3X the global prevalence of observing 15% frequency in South America.

To be able to call clades at an appropriate time, we propose to add an additional criteria to our existing four, namely:

  1. A clade shows consistent >0.10 per day growth in frequency in a country with at least 50M people and has reached >25% frequency within this country

This gives a higher bar for country-level threshold in terms of variant spread and also restricts to larger countries to reduce stochastic impacts. Here, the observation of >25% frequency requires some extrapolation from samples collected in June to frequency in mid-July, but I think is justified.

@trvrb trvrb marked this pull request as ready for review July 20, 2022 23:21
@corneliusroemer
Copy link
Member

corneliusroemer commented Jul 21, 2022

Small clarification on mutation counts to the PR description:

BA.4/5 have 3 Spike substitutions (including one reversion at 493) and one 2 AA deletion

BA.2.75 has 9 Spike substitutions (including one reversion 493)

I shall prepare a Nectclade dataset update so we don't have much delay between merging here and Nextclade putting out 22D to reduce inconsistencies.

@emmahodcroft
Copy link
Member

I think this looks great Trevor, and I like outlining this in the PR itself. We might want to also copy this over to the blog (I think a straight copy would be fine) so that one can still find all our adjustments to the clade designations in one place.

@trvrb trvrb self-assigned this Jul 21, 2022
@trvrb
Copy link
Member Author

trvrb commented Jul 21, 2022

@corneliusroemer
Copy link
Member

Asia will be most interesting - as this is where I suspect a few may be pulled in.

@trvrb trvrb merged commit 83773f6 into master Jul 22, 2022
@trvrb trvrb deleted the elevate-ba275-as-clade-22d branch July 22, 2022 04:51
@AnonymousUserUse

This comment was marked as outdated.

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.

4 participants