PartitionFinder: Difference between revisions
Moskalenko (talk | contribs) m Text replacement - "#uppercase" to "uc" |
No edit summary |
||
| Line 24: | Line 24: | ||
<!--Modules--> | <!--Modules--> | ||
== | ==Environment Modules== | ||
Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application. | |||
< | |||
==System Variables== | ==System Variables== | ||
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory | * HPC_{{uc:{{#var:app}}}}_DIR - installation directory | ||
| Line 67: | Line 64: | ||
See the [[{{PAGENAME}}_Install]] page for {{#var: app}} installation notes.|}} | See the [[{{PAGENAME}}_Install]] page for {{#var: app}} installation notes.|}} | ||
__NOTOC____NOEDITSECTION__ | __NOTOC____NOEDITSECTION__ | ||
Revision as of 18:59, 10 June 2022
Description
PartitionFinder and PartitionFinderProtein are free open source programs for selecting best-fit partitioning schemes and models of molecular evolution for nucleotide and amino acid alignments. They take the hard work out of comparing partitioning schemes, and are useful in any situation where you wish to compare or select partitioning schemes or models of molecular evolution. Both programs come together as a single download. Click below to get the appropriate download for your system.
Environment Modules
Run module spider partitionfinder to find out what environment modules are available for this application.
System Variables
- HPC_PARTITIONFINDER_DIR - installation directory
How To Run
Run PartitionFinder programs for nt or aa model analysis respectively as
PartitionFinder.py -p X DIRECTORY
and
PartitionFinderProtein.py -p X DIRECTORY
once the partitionfinder module is loaded where "X" is the number of compute cores requested in the job script and "DIRECTORY" is the full path to a folder containing a configuration file (partition_finder.cfg) and a nucleotide or aminoacid alignment in Phylip format.
Citation
If you publish research that uses partitionfinder you have to cite it as follows: Please cite Lanfear et al. (2012) if you use the tool for published research.