MetaPIGA, an Application for Phylogeny Inference
MetaPIGA is a robust implementation of several stochastic heuristics
for large phylogeny inference (under maximum likelihood), including a
random-restart hill climbing, a simulated annealing algorithm, a
classical genetic algorithm, and the metapopulation genetic algorithm
(metaGA) together with complex substitution models, discrete Gamma
rate heterogeneity, and the possibility to partition data.
MetaPIGA, application for plylogeny inference. see http://www.metapiga.org
For Site Admins:
Estimated number of jobs per day ( or week or month): 100
Estimated job submission frequency (constant flow or occasional
submission): constant flow
Planned start date: 01.09.2012
Planned completion date: 31.12.2012
Application contact person name and email: Prof. Michel Milinkovitch,
Michel.Milinkovitch AT unige.ch
SMSCG contact person: Marko Niinimaki
Application and Project Description
In a metaPIGA calculation, we start from a input dataset, a file that
contains DNA sequences of different taxa. A DNA sequence is composed
of k nucleotides (A,C, G and T). In metaGA terminology, a tree is
called an individual. The next step consist in finding the most
suitable individual, ie the phylogenetic tree that has the greatest
probability of having generating the correspondent dataset. To do, the
client program (metaPIGA) generates randomly P independent populations
of individuals (trees), which will undergo mutations and selections,
but the topological changes are guided through population comparisons.
These tasks seems to be heavy and, consequently, needs a lot of
machine resources. In the end, a consensus process, running in the
client side, will construct the final best tree based upon on the
previous P solutions issued from metaGA. It is worth reminding here
that we can not know in advance the number of trees needed to obtain
the final robust solution, meaning that metaPIGA will continue running
others analysis until the consensus process provides the best tree.
MetaPIGA is a well-known and widely used used implementation of the
# shared directory for application installation
case "$1" in
# nothing to do on the frontend
# Note: for SGE LRMS here is the place for setting the Parallel Environment
# export joboption_nodeproperty_0=mpich
# source the environment on the node and prepare MPIARGS
# Note: site needs also to make sure mpi environment works
properly ( this is normally site dependent )
# Now, calling argument is wrong or missing.
# If call was made from NorduGrid ARC, it is considered
# an error. If this script is to be used also to initialize
# MPI environment for local jobs in cluster, raising error here
# could be improper.
#$application_base_path/metapiga.sh exec file:
# is there a parameter?
if [ $# -eq 0 ]
echo "This script requires a NEXUS input file as a parameter" > /dev/stderr
#what is the location of this script?
java -jar $mydir/mp2.jar noupdate silent $*
Metapiga mp2.jar file: http://www.metapiga.org/download.html
FOR END USERS
Example data file and xrsl file.
(inputFiles= ("sample.nex" ""))
(jobname="mp test 4")
Dimensions ntax=4 nchar=15;
Format datatype=dna symbols="ACTG" missing=? gap=-;
Dir = RESULTS