Coordinating development threads for next phase of control experiment

Revision: 6

Here are checklists to guide contributors on updating the spin-up for ESM1.6:

Worked example: contributor guidelines for ACCESS ESM1.6

If there is no issue for the proposed change, create an issue in access-esm1.6-configs to describe the change and any discussions/figures/justification/testing

Create config change as a new branch in access-esm1.6-configs where the branch is based on tip of dev-preindustrial+concentrations and named using an issue number , e.g. 99-dev-preindustrial+concentrations for issue 99.

Makes changes to your branch and then open Pull Request (see screenshots)
Note that changes to restart files may need to be specified for some config changes and this specifies the restart file used;

Request for review;

Merge your changes into dev-preindustrial+concentrations.

Worked example: How to update the spin up (inputs from reviewer, contributor and runner)

Reviewer/contributor decide if a tag is going to be needed on the merged version on the dev-preindustrial+concentrations branch (a tag is used when the spin up will be updated).

Ask runner to continue run based on tagged commit.

Update experiment tables on ACCESS-Hive forum.

Worked example: runner (@Jhan) guidelines for ACCESS ESM1.6

Pull or clone fresh from the tagged commit of GitHub - ACCESS-NRI/access-esm1.6-configs: Standard ACCESS-ESM1.6 configurations released and supported by ACCESS-NRI (should be on dev-preindustrial+concentrations branch);

Continue run deciding to either use an older restart (to provide some overlapping years), parallel runs or an abrupt change;

Update experiment tables on ACCESS-Hive forum;

Update coordination table on ACCESS-Hive forum.

Please reach out to @Jhan as the runner to coordinate getting changes added. And @anton and @spencerwong for any technical guidance on contributor steps. And @clairecarouge and @cbull are available to help too.

1 Like