The description of genomic analyses in this piece about the spread of the Delta variant in the UK has major inaccuracies, and hindsight bias. 🧵
theguardian.com/commentisfree/…
Early on, the author, @chrischirp, notes that Pakistan and Bangladesh were red-listed on 9 April, but India wasn't until 23 April. There is a reasonable criticism to be made here, but it has nothing to do with variants. Cases and % positivity were already on the rise in India
We know now that delay led to hundreds of importations of the Delta variant. The article says India "first reported a concerning new variant on 24 March...so why didn’t PHE immediately escalate Delta to a variant of concern in March?"
Well, first of all, the variant reported in late March was *not* Delta / B.1.617.2, but its cousin, B.1.617.1. At the time called (ridiculously) the "double mutant": L452R and E484Q. E484Q got a lot of attention about vaccine escape b/c we had all been watching E484K variants.
But in contrast to the statement in the article that "The new Delta variant has mutations that are associated with vaccine resistance", it was B.1.617.1 that got all the early attention! And IMHO, we still don't know which mutations give Delta its advantage.
In fact, the three sub-lineages of B.1.617 were not even considered separately until 21 April, which is conveniently documented because the amazing Pango team (in this case @AineToole ) track lineage assignments in public github issues: github.com/cov-lineages/p…
So rather than being "obvious to anyone watching the relentless exponential growth of Delta during April.", it was actually pretty confusing. I make weekly VOC/VUI monitoring plots, and here's what I saw in three weeks from 19 April (1st time I included B.1.617) to 3 May.
This shows the bleeding edge of what we knew about these variants as it happened. PHE designated B.1.617.2 a VOC on 7 May: four days after the last graph above, or "eventually", as the article puts it.
And getting it right mattered: reflexively designating the whole B.1.617 super-lineage would've completely confounded both real-world and lab experiments on immunity and vaccine efficacy, because it's now clear the sub-lineages have very different biological properties.
Generating data at this scale (and there is so much more than just the genome numbers which I'm most familiar with), then analysing & synthesising a very complex and (literally) evolving picture at this speed is quite simply astonishing, and unprecedented in my scientific career.
There's a heroic cast of hundreds doing this work, from @PHE_uk, the devolved Public Health agencies, and academic partners. Too many to thank individually, but I'll single out our fearless leader, @meera_chand!

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jeffrey Barrett

Jeffrey Barrett Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jcbarret

31 May
We've pushed the weekly numbers update (thanks @theosanderson!) at covid19.sanger.ac.uk. As expected, in the most recent 2 week window, B.1.617.2 is the most common lineage in England. Still driven by local concentrations of high case numbers (L cases, R B.1.617.2):
A couple of notes on the site. We have updated the text describing ascertainment: we are no longer excluding surge tests, which make up a large fraction of all tests in key areas in recent weeks. I think this provides least biased frequencies now. Feedback welcome.
I've mentioned this before, but please be cautious interpreting proportions where we have few genomes. For example the "100%" in Dover doesn't mean much because it based on 3 genomes in the most recent 2 weeks of data:
Read 4 tweets
24 May
It's clear that B.1.617.2 has been growing faster than B.1.1.7 in UK for a few weeks. Key question for policy, not yet fully answered, is how much due to:
1. vaccine efficacy
2. intrinsic transmissibility
3. human epidemiological factors

🧵of my current thoughts on the topic:
Prelim. data show vaccines work somewhat less well against symptomatic infection w/B.1.617.2, so this makes a non-zero contribution to its recent growth. Good threads on vaccine efficacy data from PHE: &
But I think magnitude of observed VE reduction, as well as age distribution of B.1.617.2 infections, makes it unlikely to fully explain growth in UK. B.1.617.2 (blue) is a bit older than recent B.1.1.7 (green), but both more similar to each other than B.1.1.7 from December (red)
Read 16 tweets
10 May
Last week @PHE_uk designated B.1.617.2 a VOC (excellent summary from @kallmemeg below). Today we released another week's worth of surveillance genomes at covid19.sanger.ac.uk, and I'd like to walk through some of the features & findings. 🧵

First, headline result, as reported by others, is that B.1.617.2 has hit 6% in England in our 2-week rolling average (>10% in the most recent week). Other VOCs & VUIs steady.
It is hard to know exactly what this means for transmissibility. There were hundreds of imported cases in a short span, and while those are not counted here, they arrived in both a quantity and at a moment of loosening restriction that we have not seen before for other variants.
Read 7 tweets
22 Apr
Tons of new info about B.1.617 in @PHE_uk's latest technical briefing on covid #variants (which are rather excellent if I do say so). A 🧵on some key points. assets.publishing.service.gov.uk/government/upl…
First off: what is the "India variant", well, it turns out that there are actually three clades of B.1.617, which have now been termed B.1.617.1, B.1.617.2 and B.1.617.3. All three clades appeared in India, likely descended from a common ancestor there some time ago.
The "full" VUI that has garnered attention is B.1.617.1, but interestingly B.1.617.2, which does *not* have the E484Q mutation (apparent reversion) is enriched in the most recent sequences in the UK & elsewhere. So the already dumb "double mutant" label makes even less sense now.
Read 8 tweets
18 Apr
A few thoughts on the B.1.617 variant, first seen in India in late 2020, recently seen in >100 cases in the UK, and very much in the news here. TLDR: we should watch carefully, but I don't think any of our best lines of evidence on variants are yet cause for concern. 🧵
In the "variant era", there are 4 kinds of evidence we can use to evaluate a new variant: (1) how fast it is spreading in different places, (2) pre-existing info about specific mutations it carries, (3) lab experiments (ACE2 binding, Ab evasion, etc), (4) real world vaccine data.
3 & 4 are very important (at the end of the day, arguably all that matters is vaccine efficacy), but take time, even when labs around the world are focusing on these questions. I haven't seen anything yet on B.1.617, so won't comment further.
Read 12 tweets
23 Feb
There was a scary story published today in the LA Times about the "California variant" of coronavirus, but the data behind the claims are not yet published. So here's a 🧵about this variant that does have some data in it. 1/N
What's claimed in the newspaper? Well, it sounds pretty bad: "it not only spreads more readily than its predecessors, but also evades antibodies generated by COVID-19 vaccines or prior infection and is associated with severe illness and death" 2/N
That's in the first of six paragraphs of terrifying conclusions, but we then learn the study is, "currently under review by the public health departments of San Francisco County and the state...It is expected to post late this week to MedRxiv" 3/N
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(