This repo will contain standard global configurations for ACCESS-ESM1.5, the ACCESS Coupled Earth System Model.
This is an "omnibus repository": it contains multiple related configurations, and each configuration is stored in a separate branch.
Branches utilise a simple naming scheme:
{release}-{scenario}[+{modifier}]
where release signifies this is the release branch that is tested, versioned and ready for use, scenario is the base experimental design with optional modifiers. All configurations are assumed to be global extent with nominal 1 degree resolution.
Some examples of possible values of the specifiers:
where scenario is typically a CMIP experiment identifier, concentration and interactiveC describe the CO2 cycling protocol, and noLUC is no land-use change.
Most configurations are adapted from work by the CLEX CMS team.
All available configurations are browsable under the list of release branches and should also be listed below:
| Branch | Configuration Description |
|---|---|
| release-preindustrial+concentrations | Concentration driven CO2 under pre-industrial forcings |
| release-historical+concentrations | Concentration driven CO2 under historical forcings (1850-2014) |
There are more detailed notes contained in the respective branches for each configuration and release notes are posted on [this ACCESS Hive Forum topic](url.
More supported configurations will be added over time.
All configurations use payu to run the model.
This repository contains related experimental configurations to make support and discovery easier. As a user it does not necessarily make sense to clone all the configurations at once.
ACCESS-Hive contains detailed instructions for how to configure and run ACCESS-ESM1.5 with payu.
If you have questions about these configurations follow the guidelines for requesting support from ACCESS-NRI on the ACCESS Hive Forum.
This repository makes use of GitHub Actions to perform reproducibility checks on model config branches.
Config branches are branches that store model configurations of the form: release-<config> or dev-<config>, for example: release-historical+concentration. For more information on creating your own config branches, or for understanding the PR process in this repository, see the CONTRIBUTING.md.
Config tags are specific tags on config branches, whose MAJOR.MINOR version compares the reproducibility of the configurations. Major version changes denote that a particular config tag breaks reproducibility with tags before it, and a minor version change does not. These have the form: release-<config>-<tag>, such as release-historical+interactiveC-1.2.
So for example, say we have the following config tags:
release-historical+interactiveC-1.0release-historical+interactiveC-1.1release-historical+interactiveC-2.0release-historical+interactiveC-3.0This means that *-1.0 and *-1.1 are configurations for that particular experiment type that are reproducible with each other, but not any others (namely, *-2.0 or *-3.0).
*-2.0 is not reproducible with *-1.0, *.1.1 or *-3.0 configurations.
Similarly, *-3.0 is not reproducible with *-1.0, *-1.1 or *-2.0.
These checks are in the context of:
More information on submitting a Pull Request and on the specifics of this pipeline can be found in the CONTRIBUTING.md and README-DEV.md respectively.
For more information on the manually running the pytests that are run as part of the reproducibility CI checks, see model-config-tests.
The developers of ACCESS-ESM1.5 request that users of these model configurations