Create emissions driven historical configuration

[blimlim]

1. Summary:

What has changed?
This PR sets up an emissions driven historical configuration, starting from the dev-historical+concentrations configuration.

Why was this done?
An emissions driven historical configuration will be important for testing and evaluating the carbon cycle. CSIRO aims to have test runs going as soon as possible.

2. Issues Addressed:

• Set up historical+emissions configuration #369

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

I ran a prototype configuration for 5 years and compared the total CO2 emissions with the input data:

The two track well, and the damping of the minima and maxima would be expected as the model output comes from calculating a monthly mean from a linear interpolation of the original time series.

The configuration for the test used the restart for the concentration driven configuration. I'm rerunning with the correct emissions driven restart to double check that it looks ok.

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.

Swapping to emissions driven mode will change the answers

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)

The settings and input files modified here aren't 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

[blimlim]

These changes have been copied over from the dev-preindustrial+emissions configuration

[blimlim]

These changes were copied over from the dev-flat10 configuration

[github-actions]

⚠️ The Bitwise Reproducibility Check Had Errors - Check https://github.com/ACCESS-NRI/access-esm1.6-configs/actions/runs/20906508264 ⚠️
❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

• test-historical+emissions (checksums created using commit cf4d042), against
• dev-historical+emissions (checksums in commit db209a0)

Further information

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

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/20906508264/artifacts/5093069702.

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

Test summary:
🔥 test_repro_historical
🔥 test_repro_determinism

[blimlim]

!test repro commit

[github-actions]

⚠️ The Bitwise Reproducibility Check Had Errors - Check https://github.com/ACCESS-NRI/access-esm1.6-configs/actions/runs/20907365983 ⚠️
❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

• test-historical+emissions (checksums created using commit b10364f), against
• dev-historical+emissions (checksums in commit db209a0)

Further information

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

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/20907365983/artifacts/5093352370.

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

Test summary:
🔥 test_repro_historical
🔥 test_repro_determinism

[blimlim]

!test repo commit

[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/20907547499

[blimlim]

!test repro commit

[github-actions]

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

• test-historical+emissions (checksums created using commit 5161f73), against
• dev-historical+emissions (checksums in commit db209a0)

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

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/20907571612/artifacts/5093423138.

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

Test summary:
❌ test_repro_historical
✅ test_repro_determinism

[MartinDix]

Also needs updated executable and restart.

[blimlim]

!test repro commit

[github-actions]

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

• test-historical+emissions (checksums created using commit e772aa1), against
• dev-historical+emissions (checksums in commit db209a0)

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

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/22332932965/artifacts/5627800596.

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

Test summary:
❌ test_repro_historical
✅ test_repro_determinism