2/9 While we continue to see the rapid decline of non-VOCs/VOIs, the competition between B.1.1.7 & B.1.526 is quite interesting, and could have significant public health importance. Currently B.1.1.7 is "winning", though things could rapidly change as more people get vaccinated.
3/9 For the first time we saw B.1.1.7 📉 from TaqPath data, which could mean that it is slowing down (it has to at some point). Below I also plotted the B.1.1.7 frequency estimates from our sequencing data, which has tracked with TaqPath and importantly still shows B.1.1.7 📈
4/9 So I am hesitant to say that the 📈 trajectory of B.1.1.7 is starting to slow down based on the TaqPath data. We now have enough data to expect B.1.1.7 to keep 📈 until it completely dominates (>90%), or until the selection landscape changes w/ 💉
5/9 The B.1.526 story is interesting. 1st, it is a complicated lineage, with 2 new sub-lineages ("sister" lineages?) and 3 primary mutations within the spike RBD:
L452R, S477N, E484K
As you can see, they have very different patterns which could be functionally relevant.
6/9 What's interesting is that B.1.526 (+E484K or S477N) and B.1.526.2 (+S477N) were 📈 as fast as B.1.1.7, but now both are on the 📉.
B.1.526.1 (+L452R), meanwhile, is still 📈. Perhaps this is a blip in the data, or perhaps their is something real to this.🤷♂️
7/9 The L452R mutation on B.1.526.1 is notable as it is also found on the VOCs B.1.427/9 (first detected in CA) that are known to reduce the efficacy of some monoclonal antibodies. However, B.1.427/9 haven't been much of an issue in CT, and are collectively <3% since March.
8/9 The decline in B.1.526, and the fact that B.1.351 & P.1 have taken hold in CT, means that the frequency of viruses in CT with the E484K mutation has also 📉. I'll take this as good news with the caveat that other mutations are also likely important for immune evasion.
9/9 This week I'd like to highlight the work by @AndersonBrito_ who was instrumental in setting up our weekly reports. I am so grateful to have Anderson on our team 🙏
His amazing data processing python scrips and nextstrain code can be found here: github.com/andersonbrito/…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It's based on a design led by @Scalene & @pathogenomenick originally for Zika virus that was adapted for SARS-CoV-2 ("ARTIC protocol") and used by labs around the world.
Our goal was for this to be plug n' play with current SARS-CoV-2 protocols. (2/8) nature.com/articles/nprot…
The primers were designed using PrimalScheme using a pre-outbreak A.1 clade reference genome (GenBank accession: MT903345).
The scheme comprises a total of 163 primer pairs with an amplicon length ranging between 1597 and 2497 bp (average length of 1977 bp). (3/8)
Using a logistic regression of the daily frequencies, we predict that as of today (July-14), BA.5 is probably 80-90% in Connecticut.
BA.4 is still 📈 as it outcompetes BA.2, but will probably start to 📉 in frequency soon after BA.2 is gone. (2/8)
We created a new dashboard to report variant sequencing data in Connecticut. You can still access it through our main website by clicking on the "Read the latest Connecticut report" link. (3/8)
Omicron BA.2.12.1 is still 📈 in Connecticut as it is across most of the US. Fitting the % of sequenced cases to a logistic growth curve, we estimate that BA.2.12.1:
1⃣ is ~80% frequency today (May019)
2⃣ surpassed 50% in early May
3⃣ may reach 95% in early/mid June
(2/13)
From the same logistic growth curve, we also estimate that BA.2.12.1 is:
➡️ ~24% more transmissible than background (mostly other BA.2 lineages)
➡️ doubling in proportion every ~12 days
(3/13)
Based on our TaqPath PCR data (S-gene detected), we estimate that:
➡️ BA.2 is >50% in Southern Connecticut
➡️ At this rate - BA.2 will be 95% by early April
➡️ BA.2 doubling rate = 7.8 days (BA.1 in December = 3-4 days)
➡️ BA.2 ~43% more transmissible than BA.1/.1
(2/7)
Over the past 4 weeks, all of the sequenced S-gene positive samples have been Omicron BA.2 and not Delta. So we trust the 👆 PCR results reflecting the rise in BA.2. (3/7)
Here are comparative results between 10 TaqPath S-gene detected samples tested by YNHH and with our validated VOC PCR assay. Most with our assay were actually SGTF, and looking at the YNHH results, the S-gene CTs for those were 5-7 higher than N/ORF. (5/16)
We are looking into these low level spike amplification samples that should be SGTF to see if this is a lab/TaqPath assay artifact or if there is something about these BA.1 sequences. So far doesn't seem to be sequence-related. Will report (6/16)
Our initial SGTF case definition – ORF/N <30 CT, S “not detected” - was conservative to not over-call BA.1.
We updated it yesterday to include S-gene 5 CTs higher than ORF/N, and compared the results. (7/16)