Update AMIP config phenology file

[blimlim]

Closes the AMIP half of #109. See #133 for the PI config changes.

[blimlim]

!test repro

[github-actions]

✅ The Bitwise Reproducibility Check Succeeded ✅

When comparing:

• 109-AMIP-update-phenology-file (checksums created using commit b0cc473), against
• dev-amip (checksums in commit acf37f7)

Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-esm1.6-configs/b0cc473b2626b522b75c2c919c3b572692a406dd, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/43856005184.

The checksums generated by this !test command are found in the testing/checksum directory of https://github.com/ACCESS-NRI/access-esm1.6-configs/actions/runs/15574166631/artifacts/3301742430.

The checksums compared against are found here https://github.com/ACCESS-NRI/access-esm1.6-configs/tree/acf37f7971260c8ab9a8421b1c653f1030439639/testing/checksum

[JhanSrbinovsky]

@blimlim - We have an AMIP version of ESM1.6 ready? Do you know how long is the ocean forcing, and what period?

[blimlim]

Hi @JhanSrbinovsky, this is based on the ESM1.5 AMIP config, and so is still using the forcings for 1978-2014

[JhanSrbinovsky]

@blimlim I see above you've used

!test repro

This seems less applicable to myself, but I've also seen !minor bump used.

What do these do?

[blimlim]

The !test repro command runs the model config reproducibility tests. Each configuration contains file of checksums for ocean fields, generated from a 1 day run. See here for the PI config (for the AMIP config we use FINAL ABSOLUTE NORMs from the UM logs instead of the ocean checksums).

When !test repro is commented in a configuration pull request, the CI infrastructure does a new 1D run with the updated configuration, and uses the ocean checksums to check whether model answers have changed. This is useful if you have a configuration change that shouldn't change answers. You can run the !test repro command to make sure that's the case.

The comment here reports that the changes in this PR didn't affect answers (as expected).

We aim to run !test repro with each configuration pull request. If a change is expected to affect answers, then the !test repro commit command will add the updated checksums to the pull request, so that they become the new baseline to compare against. (See here for this command with the ocean field table changes).

!bump minor and !bump major can be used when releasing a configuration or a new release executable in the deployment repository. I'm a bit less on top of these, (@CodeGat will have the most knowledge!) but they update the version number in the tags and module names used for the releases.