Use latest UM executable

[blimlim]

1. Summary:

What has changed?
This PR updates the AMIP configuration to the latest deployed UM executable, in line with the changes to the coupled configurations in #429. Note that the oasis-mct and CICE changes described in #429 do not apply to this configuration. Note that UM code has not actually changed since the last deployment.

Why was this done?
This has just been done in order to keep the amip configuration up to date with the coupled configurations

2. Issues Addressed:

• Update PI control configuration to use ACCESS OASIS3-mct #402

3. Dependencies (e.g. on payu, or model)

This change requires changes to (note pull request(s) where relevant):

• workflow manager (payu):
• model deployment (ACCESS-ESM1.6):
• model component or library dependency:
• input workflow:

4. Ad-hoc Testing

What ad-hoc testing was done? How are you convinced this change is correct (plots are good)?

5. CI Testing

• !test repro has been run

6. Reproducibility

Is this reproducible with the previous commit? (If not, why not?)

• Yes
• No - !test repro commit has been run.

7. Performance

Has the model performance (say, throughput of model-years/wall-day) changed?

• Yes
• No
• N/A (if selected, please add a brief explanation why performance testing is not necessary for this PR)

If yes, provide the numbers from your testing. Is the performance better or worse?
There have not been changes to the UM code, and so performance changes aren't expected.

8. Manifests

Have you changed the executable, the input files and/or the restart files?

• Yes
• No

If yes, have you updated the manifests?

• Yes
• No

To update the manifests, run payu setup (in a cloned copy of your feature branch) with reproducibility tests turned off:

manifest:
  reproduce:
    exe: false
    input: false
    restart: false
runlog:
  enable: false

Then commit the newly created manifest files (under manifests/) only to the branch for this PR.

9. Documentation

Is the documentation updated?

• Yes
• N/A

10. Merge Strategy

• Merge commit
• Rebase and merge
• Squash

[blimlim]

!test repro

[github-actions]

❌ !test Command Failed ❌ The command given could not be parsed correctly. Usage: !test TYPE [commit] See https://github.com/ACCESS-NRI/access-esm1.6-configs/actions/runs/21814719273

[github-actions]

✅ The Bitwise Reproducibility Check Succeeded ✅

When comparing:

• 402-amip-exe (checksums created using commit c3bb468), against
• dev-amip (checksums in commit 5624bb6)

Further information

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

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/21814725960/artifacts/5427830423.

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

Test summary:
✅ test_repro_historical
✅ test_repro_determinism

[blimlim]

@aidanheerdegen just a seperate PR for using the new deployment in the AMIP config, as the namcouple and CICE changes aren't needed here

[blimlim]

Superseded by #482