🧬 PhyloRun
PhyloRun allows you to run BEAST X, BEAST 2, RevBayes, and LPhy experiments using a single tool.
📦 Installation
Use pip to install the CLI tool:
pip install --upgrade phylorun
🚀 Features
Run BEAST X, BEAST 2, RevBayes and LPhy analyses
phylorun someBeastXModel.xml
phylorun someBeast2Model.xml
phylorun someRevModel.rev
phylorun someRevModel.lphy
phylorun automatically detects which MCMC engine to use.
By default, phylorun tries to use your existing installation of the engine. If this fails, you can specify the location of the binary on your system:
phylorun --bin "/Applications/BEAST X 10.5.0/bin/beast" someBeastXModel.xml
phylorun --bin "/Applications/BEAST 2.7.7/bin/beast" someBeast2Model.xml
phylorun --bin "/usr/bin/rev" someRevModel.rev
If you don't have an engine installed on your local system, you can use the --container flag and phylorun automatically installs everything that's needed in an isolated environment:
phylorun --container someBeastXModel.xml
phylorun --container someBeast2Model.xml
phylorun --container someRevModel.rev
Currently, this does not work when your BEAST 2 analysis uses packages.
Run PhyloSpec analyses
phylorun can run a PhyloSpec analysis using any of the engines:
phylorun --engine lphy model.phylospec
Benchmark engines
You can use phylorun to see which engine is the fastest for your PhyloSpec model:
phylorun benchmark model.phylospec
Validate engines
You can use phylorun to validate that the engines produce the same results for your PhyloSpec model:
phylorun validate model.phylospec
Configuration
All unknown arguments are directly passed to the engine (put them at the end of the command):
phylorun someBeast2Model.xml -resume
For LPhy, arguments prefixed with --beast2 will be passed to BEAST 2 and not to LPhyBeast:
phylorun someLphyModel.lphy --beast2-resume
Metadata
Release files for phylorun 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| phylorun-0.10.0.tar.gz | 6.4 MB | Without provenance | Details for phylorun-0.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| phylorun-0.10.0-py3-none-any.whl | Python 3 | none | any | Details for phylorun-0.10.0-py3-none-any.whl |
Total release size: 12.9 MB
Release files / phylorun-0.10.0.tar.gz
| Download URL | phylorun-0.10.0.tar.gz |
|---|---|
| Size | 6.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3816f59b9bbe9dfeb92433edb8892b5735479f4eb1a6ca18edc803e3c15ef113
|
|
BLAKE2b-256 checksum How to use checksums |
a183699972fb5d01ae6b5376b48cc65a14b7a39b01d2c479aa8b39dd6f856a93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.1
|
Release files / phylorun-0.10.0-py3-none-any.whl
| Download URL | phylorun-0.10.0-py3-none-any.whl |
|---|---|
| Size | 6.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6b10b4f45222af79a1f5bd50eb9067501e247ee6f13d19bc90e168e76611229
|
|
BLAKE2b-256 checksum How to use checksums |
da2fa7a0a3cc21d097ed94f3aa918f53855c965f5686e64682d73d433f503b28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.1
|
Security for phylorun 0.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.