Note
Containerised conda environments for payu are now being deployed in ACCESS-NRI/model-release-condaenv so any issues with payu module versions from 1.1.6 onwards should be created there.
This repository is responsible for building, packaging and deploying payu as a micromamba environment.
In order to trigger a deployment, some steps must be followed:
- First, check that a new version of
payuhas been added to theaccessnriconda channel. This is done via CD on thepayu-org/payurepository when a new tag is pushed. - Open a PR modifying the
env.ymlfile to refer to the newly updated version ofpayu. Theenv.ymlwill be checked for validity and that the version ofpayuis defined. - When this is merged, the
env.ymlwill be used to create amicromambaenvironment. This is then packaged usingconda-pack, and deployed to the appropriate targets (eg. Gadi).
On all of the deployment targets, the deployed Payu environment can be activated using Environment Modules.
Make sure you're a member of the vk83 project! If not, see how to join an NCI project.
Important: make sure you do not have another conda environment active - either run conda deactivate or module unload any modules that are using conda.
Once you are a member, run the following:
module use /g/data/vk83/modules
module load payu/VERSIONPayu can then be invoked with payu COMMAND. See payu --help for more information.
New deployment environments must be created as a GitHub Environment and also have an entry in the config/deployment-environment.json file.
To deploy locally, you can use the assets created in the release. Releases are found here. Specifically:
- To use the compressed environment (which doesn't require conda or python) you can run
tar -xzf payu-VERSION.tar.gz payu-VERSIONand then./payu-VERSION/bin/activateto activate the environment. - To use the lockfile, you can run
micromamba create -n my-environment -f payu-VERSION.conda-lock.ymlwith an appropriate install ofmicromamba.