FastTree 2 – Approximately Maximum-Likelihood Trees for Large Alignments
By Morgan N. Price, Paramvir S. Dehal, Adam P. Arkin. PLoS ONE, 2010
13,530 citations recorded by the source corpus.
Background We recently described FastTree, a tool for inferring phylogenies for alignments with up to hundreds of thousands of sequences. Here, we describe improvements to FastTree that improve its accuracy without sacrificing scalability. Methodology/Principal Findings Where FastTree 1 used nearest-neighbor interchanges (NNIs) and the minimum-evolution criterion to improve the tree, FastTree 2 adds minimum-evolution subtree-pruning-regrafting (SPRs) and maximum-likelihood NNIs. FastTree 2 uses heuristics to restrict the search for better trees and estimates a rate of evolution for each site (the “CAT” approximation). Nevertheless, for both simulated and genuine alignments, FastTree 2 is slightly more accurate than a standard implementation of maximum-likelihood NNIs (PhyML 3 with default settings). Although FastTree 2 is not quite as accurate as methods that use maximum-likelihood SPRs, most of the splits that disagree are poorly supported, and for large alignments, FastTree 2 is 100–1,000 times faster. FastTree 2 inferred a topology and likelihood-based local support values for 237,882 distinct 16S ribosomal RNAs on a desktop computer in 22 hours and 5.8 gigabytes of memory. Conclusions/Significance FastTree 2 allows the inference of maximum-likelihood phylogenies for huge alignments. FastTree 2 is freely available at http://www.microbesonline.org/fasttree.
Subfields: Genetics, Molecular Biology
View Paper: https://www.semanticscholar.org/paper/d5677974ad0a645fbb71a6dc0355c54005239882
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Genetics
- Olivier Gascuel
- Siavash Mirarab
- Alexandros Stamatakis
- Erfan Sayyari
- Steven Kelly
- Morgan N. Price
- Robert C. Edgar
- David M. Emms
In Molecular Biology
- Rob Knight
- Peer Bork
- Curtis Huttenhower
- Noah Fierer
- Robert C. Edgar
- J. Gregory Caporaso
- Patrick D. Schloss
- Johannes Söding
Citations in the corpus
- Effects of diurnal variation of gut microbes and high fat feeding on host circadian clock function and metabolism (2015, positive): “, 2007), and a phylogenetic tree built using FastTree (Price et al., 2010).”
- ClonalFrameML: Efficient Inference of Recombination in Whole Bacterial Genomes (2015, methodology): “One of the most popular approaches to do this is the maximum likelihood (ML) method, as implemented for example in PhyML [16], RAxML [17] and FastTree [18].”
- EMIRGE: reconstruction of full-length ribosomal genes from microbial community short read sequencing data (2011, methodology): “A tree was built using FastTree [52], and weighted UniFrac values were computed for each pair of communities using this single phylogeny.”
- Clustal Omega for making accurate alignments of many protein sequences (2018, methodology): “Where we used maximum likelihood trees as external guide-trees for Clustal Omega, these were constructed from the reference alignment using FastTree2.”
- Soil pH mediates the balance between stochastic and deterministic assembly of bacteria (2018, positive): “construct a maximum-likelihood tree in FastTree [40].”
- New evidences on the altered gut microbiota in autism spectrum disorders (2017, methodology): “The phylogenetic tree was inferred using micca-phylogeny [70].”
- Bifidobacteria or fiber protect against diet-induced microbiota-mediated colonic mucus deterioration (2017, methodology): “, 2010b) and used to build a phylogenetic tree with FastTree (Price et al., 2010), which was used to calculate α- and β-diversity of samples using Phylogenetic Diversity (Faith, 1992).”
- PhyloPhlAn is a new method for improved phylogenetic and taxonomic placement of microbes (2013, methodology): “This most current phylogenetic tree is reconstructed with RAxML version 7.3.2 28 in place of FastTree 33 to increase accuracy at the expense of computational time (620 instead of 2 CPU-hours).”