Running the BEAST requires:
Python >= 3.8
One easy way to obtain the above is through the AstroConda Python stack:
First install Miniconda which contains the conda package manager. Once Miniconda is installed, you can use the
condacommand to install any other packages and create environments, etc.
Create a conda environment for the BEAST. Replace <env_name> with the name of the conda environment you want (e.g.,
beast). The specific version of python can be different than 3.11, note it must be at least 3.8.
$ conda create -n <env_name> python=3.11
Switch to this newly create conda environment
$ conda activate <env_name>
Installation for Users¶
In addition to installing the code, library files also need to be installed. See BEAST Library Files.
beast can be installed using pip. This installs the latest released version.
$ pip install beast
If you already have an older version installed, use:
$ pip install --upgrade beast
Or, from the repository directly. This installs the development version with the latest features.
$ pip install git+https://github.com/BEAST-Fitting/beast.git
If you are happy with your current environment,
beast can also be installed from
the source code in the normal python fashion after cloning from the git repo or
downloading from Github
$ pip install .
If you are using conda, you may wish to create a conda environment with the dependencies before doing the install
$ conda env create -n beast --file conda-environment.yml
$ conda activate beast
$ pip install .
Installation for Developers¶
If you plan on modifying the
beast in addition to running the code, it may
be useful to create a development installation. First, create a fork of the
beast repository and clone it:
$ git clone https://github.com/YourName/beast.git
Optionally, you can rename this cloned copy:
$ git clone https://github.com/YourName/beast.git beast-YourName
Set the value of the fork’s ‘upstream’ to the official distribution so you can incorporate changes made by others to your development fork. In the clone of your fork, run the following:
$ git remote add upstream https://github.com/BEAST-Fitting/beast.git
In order to run a development installation, navigate to the directory in your
beast repository that contains
setup.py, and run:
$ pip install -e .
Installation for Production Runs¶
Using a dedicated conda environment for production BEAST runs may be desirable. Such an environment provides a way to ensure that production runs are reproducible by fixing the versions of all the software used.
Create a conda environment, and name it differently from your default and other environments:
$ conda create -n beast_production python=3.11
Activate the environment after all the packages are finished installing:
$ conda activate beast_production
Install dependencies using conda (better for speed):
$ conda install astropy scipy h5py matplotlib cython
Next, install the BEAST. You have three options:
Option 1: Use pip to install a stable version of the BEAST (e.g. v2.0):
$ pip install beast==2.0
Option 2: Get the latest production branch, which can be ahead of the pypi version:
$ pip install git+https://github.com/BEAST-Fittingfirstname.lastname@example.org
Option 3: If you’ll be doing development, follow the instructions above (Installation for Developers). Note that you can make separate environments for development and production modes.
The BEAST production version is now ready for use. Note, you need to activate this conda environment every time you want to use this installed version.
BEAST Library Files¶
For the BEAST to work properly, you need to place a set of files in a directory. These files contain information related to filters, stellar atmospheres, and in the future stellar evolution models.
The required library files can be manually acquired from:
Note that the archive at this link contains a folder called
contents of this folder are the library files required by the BEAST. These files need to be placed within (any of) the possible locations specified in Location.
Alternatively, after installing the BEAST, run the following script and the library files will be downloaded into the location specified in Location:
$ beast get_libfiles
There are 2 possible locations for the required library files. The possible locations are (in the order the code will search for them):
In a directory designated by a BEAST_LIBS environment variable.
.beastdirectory in the home directory of the current user (ie,
~/.beast); this is usually the easiest and will be automatically created if it doesn’t exist.