Use aerosols with updated 1849 and 2023 data

[blimlim]

1. Summary:

What has changed?
The historical aerosol ancillaries have been updated to use data from the CMIP7 inputs in the boundary years 1849 and 2023. See ACCESS-NRI/CMIP7-Input#119
Previously these years used duplicate data from 1850 and 2022.

This PR adds the updated ancillaries to the configuration.

Why was this done?
This change was made for consistency with the CO2 emissions files. The impacts are expected to be minimal, as only aerosol values seen by the model in Jan 1850 and Dec 2022 will be affected.

2. Issues Addressed:

• Update historical and AMIP aerosols #353

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

See plots of the total aerosol emissions in ACCESS-NRI/CMIP7-Input#119

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.

Aerosol values seen by the model differ in the first month

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)

Input files 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:

• 353-historical-1849+2023-aerosols (checksums created using commit ae537fa), against
• dev-historical+concentrations (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/ae537fa4f1509240c8740e6b8b7591c380091819, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/59643501876.

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/20769727086/artifacts/5044952115.

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