The use of representative community samples to assess SARS-CoV-2 lineage competition: Alpha outcompetes Beta and wild-type in England from January to March 2021
Bibliographic record
Abstract
Genomic surveillance for SARS-CoV-2 lineages informs our understanding of possible future changes in transmissibility and vaccine efficacy and will be a high priority for public health for the foreseeable future. However, small changes in the frequency of one lineage over another are often difficult to interpret because surveillance samples are obtained using a variety of methods all of which are known to contain biases. As a case study, using an approach which is largely free of biases, we here describe lineage dynamics and phylogenetic relationships of the Alpha and Beta variant in England during the first 3 months of 2021 using sequences obtained from a random community sample who provided a throat and nose swab for rt-PCR as part of the REal-time Assessment of Community Transmission-1 (REACT-1) study. Overall, diversity decreased during the first quarter of 2021, with the Alpha variant (first identified in Kent) becoming predominant, driven by a reproduction number 0.3 higher than for the prior wild-type. During January, positive samples were more likely to be Alpha in those aged 18 to 54 years old. Although individuals infected with the Alpha variant were no more likely to report one or more classic COVID-19 symptoms compared to those infected with wild-type, they were more likely to be antibody-positive 6 weeks after infection. Further, viral load was higher in those infected with the Alpha variant as measured by cycle threshold (Ct) values. The presence of infections with non-imported Beta variant (first identified in South Africa) during January, but not during February or March, suggests initial establishment in the community followed by fade-out. However, this occurred during a period of stringent social distancing. These results highlight how sequence data from representative community surveys such as REACT-1 can augment routine genomic surveillance during periods of lineage diversity.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".