Set up historical + emissions configuration by blimlim · Pull Request #535 · ACCESS-NRI/access-esm1.6-configs

blimlim · 2026-03-06T03:26:31Z

1. Summary:

What has changed?

This PR sets up a historical+emissions configuration. Starting with the dev-historical+concentrations configuration, it adds the CMIP7 CO2 emissions file, activates the interactive carbon cycle, and removes the prescribed CO2 concentrations from the namelist.

The CO2 emissions file is a copy of the one produced here: ACCESS-NRI/CMIP7-Input#118 (comment)

This uses the same restart as the dev-historical+concentrations configuration, as the CO2 3D tracers have already been set to 4.3189e-4, allowing the restart to be used for both the concentration and emissions driven configuration.

The maximum number of ancillary lookups NANCIL_LOOKUPSA has been increased to 105000 to allow for the longer time period in the ozone ancillary. This change will be cherry picked to all branches.

Why was this done?
This configuration is being set up for the fast track experiments.

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

Using an earlier test version of the configuration, 5 years of model output CO2 emissions were compared with the input data:

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)

The change in input files is 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 · 2026-03-06T03:26:43Z

!test repro commit

atmosphere/namelists

…1.6-configs/actions/runs/22747681004

github-actions · 2026-03-06T03:33:47Z

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

369-historical+emissions (checksums created using commit 2e37e99), against
dev-historical+emissions (checksums in commit 0ec7135)

🔧 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/pr535/369-historical+emissions/2e37e99591540c63c2500059e47fa02b38af5862, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/65975481224.

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/22747681004/artifacts/5791333881.

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

Test summary:
❌ test_repro_historical
✅ test_repro_determinism

MartinDix · 2026-03-06T03:51:13Z

Looks ok, but README still says concentration

MartinDix

Looks good

blimlim · 2026-03-06T04:56:31Z

!cherry-pick 2e37e99 into dev-preindustrial+concentrations dev-preindustrial+concentrations+CN dev-amip dev-amip+CN dev-historical+concentrations dev-historical+concentrations+CN dev-4xCO2+concentrations dev-4xCO2+concentrations+CN dev-preindustrial+emissions dev-preindustrial+emissions+CN dev-1pctCO2 dev-1pctCO2+CN dev-1pctCO2-rad dev-1pctCO2-rad+CN dev-1pctCO2-bgc dev-1pctCO2-bgc+CN dev-flat10 dev-flat10+CN

github-actions · 2026-03-06T04:56:56Z

Automatic Git cherry-picking of commit(s) 2e37e99 into dev-amip 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:

Create new branch from target branch:

git checkout dev-amip
git pull
git checkout -b cherry_pick_from_pr535_into_dev-amip

Cherry-pick commits:

git cherry-pick 2e37e99591540c63c2500059e47fa02b38af5862

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

git push --set-upstream origin cherry_pick_from_pr535_into_dev-amip

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

github-actions · 2026-03-06T04:56:57Z

Automatic Git cherry-picking of commit(s) 2e37e99 into dev-amip+CN 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:

Create new branch from target branch:

git checkout dev-amip+CN
git pull
git checkout -b cherry_pick_from_pr535_into_dev-amip+CN

Cherry-pick commits:

git cherry-pick 2e37e99591540c63c2500059e47fa02b38af5862

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

git push --set-upstream origin cherry_pick_from_pr535_into_dev-amip+CN

Open a new pull request on github making sure the target branch is set to dev-amip+CN.

github-actions · 2026-03-06T04:56:58Z

Automatic Git cherry-picking of commit(s) 2e37e99 into dev-preindustrial+emissions was successful.