Journal article
Rate variation and recurrent sequence errors in pandemic-scale phylogenetics
- Abstract:
- Phylogenetic analyses of genome sequences from infectious pathogens reveal essential information regarding their evolution and transmission, as seen during the coronavirus disease 2019 pandemic. Recently developed pandemic-scale phylogenetic inference methods reduce the computational demand of phylogenetic reconstruction from genomic epidemiological datasets, allowing the analysis of millions of closely related genomes. However, widespread homoplasies, due to recurrent mutations and sequence errors, cause phylogenetic uncertainty and biases. We present algorithms and models to substantially improve the computational performance and accuracy of pandemic-scale phylogenetics. In particular, we account for, and identify, mutation rate variation and recurrent sequence errors. We reconstruct a reliable and public sequence alignment and phylogenetic tree of >2 million severe acute respiratory syndrome coronavirus 2 genomes encapsulating the evolutionary history and global spread of the virus up to February 2023.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 5.0MB, Terms of use)
-
(Preview, Other, pdf, 1.2MB, Terms of use)
-
- Publisher copy:
- 10.1038/s41592-025-02932-8
Authors
- Publisher:
- Nature Research
- Journal:
- Nature Methods More from this journal
- Volume:
- 23
- Issue:
- 3
- Pages:
- 565-573
- Publication date:
- 2026-02-09
- Acceptance date:
- 2025-10-24
- DOI:
- EISSN:
-
1548-7105
- ISSN:
-
1548-7091
- Language:
-
English
- Keywords:
- Pubs id:
-
2372517
- Local pid:
-
pubs:2372517
- Source identifiers:
-
3850272
- Deposit date:
-
2026-03-13
- ARK identifier:
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
Terms of use
- Copyright date:
- 2026
- Licence:
- CC Attribution (CC BY) 3.0 IGO DEED
If you are the owner of this record, you can report an update to it here: Report update to this record