Deployment

All released versions of ACCESS-ESM1.6 configurations come with a pre-deployed build on Gadi. Deployed builds are stored under the project vk83. You can see all deployed builds via:

module use /g/data/vk83/modules
module avail access-esm1p6

There are builds deployed for development only (identified with a dev_ prefix to the date tag) and released deployments (identified with only a date tag). Up-to-date model configurations use the latest full released build.

These deployments are optimised for the Sapphire-Rapid hardware from Intel (i.e., the normalsr queue), and will run slower on Cascade-Lake (i.e., the normal queue). In general, these deployments won't run on other NCI hardware.

Release information

The deployment process creates a GitHub release with the same tag as the deployed module. All releases are available under the Releases page. Each release has a changelog and meta-data with detailed information about the build and deployment, including:

• paths on Gadi to all executables built in the deployment process (spack.location file)
• a spack.lock file, which is a complete build provenance document, listing all the components that were built and their dependencies, versions, compiler version, build flags and build architecture
• the environment file spack.yaml used for the deployment

Deployment process

The deployment is managed via GitHub Actions that are triggered when a new version of the spack.yaml file is committed to the main branch or a dedicated backport/VERSION branch of the ACCESS-NRI/ACCESS-ESM1.6 repository. Refer to the Building page for information on creating new model build versions.

No manual deployments will be accepted.