Update to new restart

[blimlim]

1. Summary:

What has changed?
This changes the restart to a copy of /scratch/p66/txz599/access-esm/archive/pi-esm-01-expt-2c021aa7/restart200 with the year changed to 1, as required for the rerun of the preindustrial+emissions simulation.

Why was this done?

2. Issues Addressed:

• New restart for preindustrial+emissions #661

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.

Answer changing due to new restart being used

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)

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 commit

[github-actions]

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

• 661-preindustrial+emissions-restart (checksums created using commit db3e892), against
• dev-preindustrial+emissions (checksums in commit ccdce9f)

🔧 The new checksums will be committed to this PR, if they differ from what is on this branch.

Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-esm1.6-configs/pr662/661-preindustrial+emissions-restart/db3e892a4bbb09e9f86ab44edfb207739281e4e7, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/69643725286.

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/23884039860/artifacts/6235063586.

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

Test summary:
❌ test_repro_historical
✅ test_repro_determinism

[MartinDix]

OK

[JhanSrbinovsky]

I'll get these started when I get back from picking up kids

[blimlim]

Thanks @JhanSrbinovsky – I haven't quite got the diagnostics changes into the emissions driven configs (they need a separate PR). Working on them now and will let you know when they are ready to go.

[blimlim]

!cherry-pick 289abf3 into dev-flat10

[github-actions]

Automatic Git cherry-picking of commit(s) 289abf3 into dev-flat10 failed. This usually happens when cherry-picking results in a conflic or an empty commit. To manually cherry-pick the commits and open a pull request, please follow these instructions:

1. Create new branch from target branch:

git checkout dev-flat10
git pull
git checkout -b cherry_pick_from_pr662_into_dev-flat10

2. Cherry-pick commits:

git cherry-pick 289abf3

3. Fix any conflicts and/or empty commits by following the instructions provided by Git.
4. Push the new branch:

git push --set-upstream origin cherry_pick_from_pr662_into_dev-flat10

5. Open a new pull request on github making sure the target branch is set to dev-flat10.

[blimlim]

!cherry-pick db3e892 into dev-flat10

[github-actions]

Automatic Git cherry-picking of commit(s) db3e892 into dev-flat10 was successful.

The new pull request can be reviewed and approved here.