MrBayes: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Marked this version for translation)
No edit summary
Line 46: Line 46:
==== MPI ==== <!--T:11-->
==== MPI ==== <!--T:11-->
The following job script will use 8 CPU cores in total, on one or more nodes.   
The following job script will use 8 CPU cores in total, on one or more nodes.   
Like the previous example it uses an input file (<code>primates.nex</code>) distributed with MrBayes.
Like the previous example, it uses an input file (<code>primates.nex</code>) distributed with MrBayes.


<!--T:36-->
<!--T:36-->
Line 74: Line 74:
==== GPU ==== <!--T:17-->
==== GPU ==== <!--T:17-->
The following job script will use a GPU.
The following job script will use a GPU.
Like the previous examples it uses an input file (<code>primates.nex</code>) distributed with MrBayes.
Like the previous examples, it uses an input file (<code>primates.nex</code>) distributed with MrBayes.


<!--T:37-->
<!--T:37-->
Line 102: Line 102:


== Checkpointing == <!--T:23-->
== Checkpointing == <!--T:23-->
If you need very long runs of MrBayes, we suggest you break up the work into several small jobs rather than one very long job. Long jobs have are more likely to be interrupted a hardware failure or a maintenance outage. Fortunately, MrBayes has a mechanism for creating checkpoints, in which progress can be saved from one job and continued in a subsequent job.
If you need very long runs of MrBayes, we suggest you break up the work into several small jobs rather than one very long job. Long jobs have are more likely to be interrupted by hardware failure or maintenance outage. Fortunately, MrBayes has a mechanism for creating checkpoints, in which progress can be saved from one job and continued in a subsequent job.


<!--T:38-->
<!--T:38-->
rsnt_translations
56,420

edits

Navigation menu