2/10 Our data combined with the CDC indicates that Delta was ~64% by 6/28 in Connecticut and may have been as high as 80% by 7/6 (remember that sequencing data always has a bit of a lag). Also, the rise in Delta is replacing almost all other variants.
3/10 In addition to B.1.617.2, we are also seeing the sub-lineages AY.1, AY.2, and AY.3, which are all classified as Delta. Some AY.1's have K417N and some AY.2's have V70F. AY.3 is defined by mutations outside of spike. The functional differences between these are unknown.
4/10 The increase in Delta combined with low vaccination rates has caused a resurgence of COVID-19 cases in some states. In Connecticut, we are only seeing a very slight increase so far, which is also reflected in the wastewater data.
5/10 Follow @thehowie for a regular breakdown of the case numbers in Connecticut π
6/10 If Delta is up, but not so much the cases - how do we estimate the potential impact of Delta?
To help answer this question, we added a new function to our reports: Variant-specific effective reproduction numbers (Rt)
7/10 We estimate Rt by combining the variant frequency estimates from our sequencing data with daily reported COVID-19 cases. @MaryPetrone10 + @jessroth95 developed this method to compare the transmissibility of Alpha vs Iota.
8/10 We estimate that the Rt for Delta is > 1 (1.55, indicating that cases are π), and is ~2X greater than Alpha (0.67) in CT. Unless we drive the Delta Rt < 1 though vaccinations and NPIs, we should absolutely expect to see an increase in local cases.
9/10 Delta is now dominant in CT, and only monitoring its frequency will become less informative (at least until something new emerges...). Following Rt trends will tell us a lot more about what to expect. Currently the Delta Rt is going in the wrong direction.
10/10 This week I'd like to thank @rtobiaskoch, @kendallbillig, @jessroth95, @ChaneyKalinich, @RebeccaEarnest1 for quickly implementing the Rt plots to our reports this week. It's still a work in progress (e.g. need to add CIs), and we appreciate constructive feedback π»
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
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 π)
2/8 In Connecticut, the % of sequenced cases that are the Delta variant (B.1.617.2) decreased in recent weeks. This is probably more of a reflection of noisy data when trying estimate frequencies from a small number of cases vs an actual decline in delta.
3/8 Looking at our neighbors in Massachusetts and New York, delta is 10-20%, so we in Connecticut are probably pretty close to that. My guess is that we'll see a π in delta in the coming weeks to reflect the trends of our neighbors.
2/7 Gamma (P.1) and Delta (B.1.617.2) continue rising in Connecticut, while Alpha (B.1.1.7) and others decline, following national trends (see next tweet).
3/7 Data from outbreak.info shows that in the US πΊπΈ, Delta (B.1.617.2) is π exponentially, while Alpha (B.1.1.7) is on the π. Despite this, COVID-19 cases are still dropping (for now).
2/6 We now have 8 cases of B.1.617.2 (5 shown in the π²) and 2 of B.1.617.1. To my knowledge, none of these are associated with βοΈ. Our phylo π² shows that there are at least 4 independent transmission chains of these viruses, spanning at least 3 counties. Definately one to π
3/6 The π in B.1.1.7 shown in tweet 1 is probably a combination of noisy data with few cases and the emergence of other lineages. The figure π 1 is from TaqPath SGTF data, which is a week ahead of the sequencing shown π, where we don't yet see the sudden π.
2/5 The second case of B.1.617.2 was from the same county as the first case (Fairfield), but they are unrelated (see tree π). Neither cases are known to be linked to international travel.
3/5 B.1.1.7 is still π frequency not because the lineage is rapidly expanding, but because it is dying out slower than the non-B.1.1.7 lineages. So the total number of B.1.1.7 cases π by 87% since late March.
2/7 B.1.617 first reported in India comes in 4 different flavors primarily defined by their spike gene mutations. While the CDC currently recognizes all 4 as VOIs, the B.1.617.2 lineage that we detected importantly does not have the E484Q mutation.
3/7 The B.1.617.2 case was not associated with travel, suggesting that there is some level of local transmission. Though the presence of other highly transmissible variants in CT - like B.1.1.7 - may limit its ability to become established.