historical+concentrations: new restart

[blimlim]

1. Summary:

What has changed?

This PR cherry picks the changes from #473 into the historical+concentrations configuration, specifically:

• updates the restart to a copy of the latest dev-preindustrial+concentrations restart. The year was updated to 1850 following the steps here: https://access-nri.github.io/access-esm1.6-configs/inputs/restarts/#changing-the-date-of-restart-files
• The 3D CO2 fields in this copy were replaced with the pre-industrial value of 4.3189e-4 following the procedure here - This has no effect on this configuration, however allows for the restart file to also be used for the historical+emissions configuration (see Create emissions driven historical configuration #370)
• UM code and MOM namelist changes to allow starting from year 1 (these don't have any effect for this configuration).

Why was this done?

2. Issues Addressed:

• Configurations for February spinup #472

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)?

To confirm that resetting the 3D CO2 fields in the atmosphere restart doesn't affect concentration driven runs, I ran 2 year long experiments using restarts with and without the modified CO2 fields.

Based on the ice restarts, the two runs matched:

nccmp -dg emiss-co2/archive/restart001/ice/iced.1852-01-01-00000.nc orig-co2/archive/restart001/ice/iced.1852-01-01-00000.nc

(note the atmosphere restarts and outputs will differ, but only for the 3D CO2 fields)

Additional testing performed in #472

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.

Answers change due to the change in restart

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)

Restart change not expected to affect performance

If yes, provide the numbers from your testing. Is the performance better or worse?

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:

• historical-feb-updates (checksums created using commit 6c23524), against
• dev-historical+concentrations (checksums in commit 732c520)

🔧 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/6c235243734bc74ca078e85a93bf7fcfd81f3041, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/64623381544.

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/22334196088/artifacts/5628242066.

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

Test summary:
❌ test_repro_historical
✅ test_repro_determinism

[MartinDix]

OK