Nathan Grubaugh Profile picture
Jul 1, 2021 9 tweets 5 min read Read on X
🧬7/1 Connecticut #SARSCoV2 variant surveillance
@CovidCT | @jacksonlab | @CTDPH | @YaleSPH | @Yalemed

Alpha (B.1.1.7) = 50% (📉9%)
Delta (B.1.617.2) = 13.6% (📈11%)

short 🧵 | Report 👉
covidtrackerct.com/variant-survei…
2/9 Last week when we reported that Delta was only 2.3% I said: "This is probably more of a reflection of noisy data when trying estimate frequencies from a small number of cases", and followed that up with an expectation that we will see Delta 📈.

3/9 This week we are seeing the expected 📈 in Delta (B.1.617.2), but the caveat still remains that our estimates are noisy because of the low numbers of sequenced cases (a product of the low numbers of cases, which is a good problem to have 👍)
4/9 To improve our weekly estimates, we are now also including recently sequenced data from the CDC (typically samples tested by Quest Diagnostics).
5/9 Interestingly, the frequency of "Other variants" is going 📈 for the first time since our variant surveillance began in early 2021 (see 2x 👆). We are finding that this is being driven by lineage B.1.621.
6/9 While B.1.621 is not yet listed as a variant of concern/interest, but it has both the E484K and N501Y mutations found in Beta (B.1.351) and Gamma (P.1) that are known to decrease the efficacy of some vaccines. (source = outbreak.info)
7/9 B.1.621 represents <1% of the cases in the US and has not been detected in many places of the world.

**However**, B.1.621 represents ~15% of the sequenced cases in Colombia, and is recently trending 📈 in association with 📈 cases. (source = outbreak.info)
8/9 This is not to say that B.1.621 will become a concern here, I'm primarily highlighting what our surveillance system is intended to do: detect emerging lineages so that we can understand its epidemiology and inform public health. I'll provide updates as we learn more.
9/9 I'd like to thank the @CDC_AMD program, especially @dmaccannell, for not only providing financial support for sequencing, but also for 📈 their sequencing efforts to enhance our surveillance program in Connecticut. We greatly appreciate their commitment to open data sharing💪

• • •

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

Keep Current with Nathan Grubaugh

Nathan Grubaugh 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 @NathanGrubaugh

Jul 15, 2022
⚡️We developed & performed initial validation on an amplicon-based sequencing protocol (PrimalSeq) for Monkeypox virus (MPXV).

It improves genome coverage compared to metagenomic sequencing, especially at CTs >20.

🧵 1/8 | Protocol 👉
protocols.io/view/monkeypox…
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)
Read 8 tweets
Jul 14, 2022
🧬July-14 Connecticut #SARSCoV2 variant surveillance
@CovidCT|@CTDPH|@CDC_AMD|@YaleSPH|@Yalemed

📈BA.5 is now the dominant variant in CT (53% from 6/27-7/4), followed by BA.2 (34% & 📉) and BA.4 (11% & 📈)

🚫No detection of BA.2.75

🧵 (1/8) | Report 👉
kphamyale.shinyapps.io/variant_report/
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)

👉 covidtrackerct.com
Read 8 tweets
May 19, 2022
🧬May-19 Connecticut #SARSCoV2 variant surveillance
@CovidCT|@CTDPH|@CDC_AMD|@YaleSPH|@YaleMed

📊Sequencing last 3 weeks
➡️ BA.2.12.1 = 44% (📈 8%)
➡️ BA.2 (other lineages) = 56% (📉 7%)
➡️ BA.4/5 = 0.3% (5 total)

🧵 (1/13) | Report 👉
covidtrackerct.com/variant-survei… Image
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) Image
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) Image
Read 15 tweets
May 5, 2022
🧬May-5 Connecticut #SARSCoV2 variant surveillance
@CovidCT|@CTDPH|@CDC_AMD|@YaleSPH|@Yalemed

Last 3 weeks
➡️BA.1.1 = 4%
➡️BA.2.12.1 = 23% (may be slowing down)
➡️BA.2 (other lineages) = 73%
➡️BA.4/BA.5 = 0% (might still be coming)

🧵 (1/9) | Report 👉
covidtrackerct.com/variant-survei…
We no longer have TaqPath data from YNHH to track SGTF, but we will use our "VOC" PCR assay that detect SGTF and ORF1a target failures (ORFTF).

BA.1 = SGTF
BA.2 = ORFTF

BA.1 is barely hanging on. (2/9)
👆 here is the "VOC" PCR assay referenced above. (3/9)

journals.plos.org/plosbiology/ar…
Read 9 tweets
Mar 17, 2022
🧬 March-17 Connecticut #SARSCoV2 variant surveillance
@CovidCT | @CTDPH | @CDC_AMD | @YaleSPH | @Yalemed

📊Sequencing data last 3 weeks
BA.1/.1 = 84%📉
BA.2 = 16%📈
Delta = 0%

📊PCR data this week
BA.1/.1 = 41%📉
BA.2 = 59%📈

🧵 (1/7) | Report 👉
covidtrackerct.com/variant-survei…
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)
Read 8 tweets
Feb 3, 2022
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) Image
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) Image
Read 13 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(