Difference between revisions of "MP-EST"

Jump to navigation Jump to search
(Created page with "Category:SoftwareCategory:BioinformaticsCategory:Phylogenetics {|<!--CONFIGURATION: REQUIRED--> |{{#vardefine:app|mpest}} |{{#vardefine:url|https://code.google.com...")
Line 78: Line 78:
<!--Turn the Table of Contents and Edit paragraph links ON/OFF-->
<!--Turn the Table of Contents and Edit paragraph links ON/OFF-->
* Validated 4/5/2018

Revision as of 18:56, 5 April 2018


mpest website  

The MP-EST method estimates species trees from a set of gene trees by maximizing a pseudo-likelihood function. The program is written in C. The parallel version of the program can run independent searches (chains) in parallel. Each chain starts with a different seed. The program will find the estimate of the species tree with the largest likelihood score across chains. To use MP-EST, you need to create two files; a gene tree file and a control file.

The gene tree file contains rooted ML gene trees. Because mp-est can only take gene trees with branch lengths, please make sure that all gene trees have branch lengths, though mp-est does not use branch length information to reconstruct species trees. Unrooted ML gene trees (with branch lengths) can be estimated from sequences using phylogenetic programs (phyml, phylip). The unrooted ML trees can be rooted in phybase using the outgroup. The control file contains necessary parameters for running MP-EST (for example, seed, number of species, user tree).

To construct MP-EST trees:

  1. Estimate ML gene trees (w/o branch lengths) from phylogenetic programs (phyml, phylip, paup).
  2. Root ML gene trees (gene trees estimated from phyml are unrooted trees).
  3. Put the rooted ML gene trees (phylip format) into a single file (this is the gene tree file).
  4. Create a control file for running MP-EST (see Manual for how to create a control file).
  5. Type “mpest control” (if the control file is named "control ") to run mp-est .

Required Modules


  • mpest

System Variables

  • HPC_{{#uppercase:mpest}}_DIR - installation directory
  • HPC_{{#uppercase:mpest}}_BIN - executable directory
  • HPC_{{#uppercase:mpest}}_DOC - documentation directory


  • Validated 4/5/2018