Coordinating development threads for next phase of control experiment

CMIP7 CMIP7 development
1

As discussed here at the ESM1.6 standup 20/05/2025, this thread is to discuss and plan the upcoming combining of ESM 1.6 dev work to continue the existing Jhan simulation.

Please edit the below table with the name of the proposed update (this post is a wiki so anyone can edit it), it’s priority, target date and related github issue.

Proposed update Priority Target Date (ready) GitHub Issue/PR
Technical, I/O etc
Build system changes (see below) Update mom5 SPR for new CMake build system by dougiesquire · Pull Request #238 · ACCESS-NRI/spack-packages · GitHub
code change: radiation / bgc only experiments 1
MOM grid format update (area changes) Update ocean grid inputs to mosaic format · Issue #31 · ACCESS-NRI/access-esm1.6-configs · GitHub
Wombat diagnostics to be output for assessing model 1 Added to branch 5/5/25 Update diag_table_wombatlite by dougiesquire · Pull Request #107 · ACCESS-NRI/access-esm1.6-configs · GitHub
Atmosphere STASH changes 0 Added to branch 16/5/25 Pull requests · ACCESS-NRI/access-esm1.6-configs
Switch to oneAPI compiler + use recent dependencies (MPI, NetCDF) 0 13-Jun Added the known working version for oneapi by manodeep · Pull Request #98 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub
Reset sea-level? 2
CABLE as a library
Read number of phenology types from file Added to branch 11/6/25 Update phenology file by blimlim · Pull Request #133 · ACCESS-NRI/access-esm1.6-configs · GitHub
Science changes
Australian PFTs 1 Add Australian PFTs · Issue #106 · ACCESS-NRI/access-esm1.6-configs
Canopy height 2 Test spatially and temporally varying canopy height · Issue #108 · ACCESS-NRI/access-esm1.6-configs
CICE5 0 13-Jun Create test config for cice5 integration · Issue #80 · ACCESS-NRI/access-esm1.6-configs · GitHub
cleaning up the vegetation distribution (so land use change is working) 0 TBD: Produce Land Use ancillaries for the ACCESS-ESM1.6 piControl experiments · Issue #54 · ACCESS-NRI/CMIP7-Input
Root distribution 2
Alternate vcmax feedback 1
Wombat parameter change (alkalinity gradient) 0 Added to branch 4/6/25 Dev preindustrial+concentrations pjb update1 by pearseb · Pull Request #126 · ACCESS-NRI/access-esm1.6-configs · GitHub
Wombat parameter change (disscal) 0 Added to branch 11/6/25 Update field_table by pearseb · Pull Request #132 · ACCESS-NRI/access-esm1.6-configs · GitHub
deep_cmt_opt Deep CMT option · Issue #121 · ACCESS-NRI/access-esm1.6-configs
Mediterranean ocean bathymetry change? 1 Change bathymetry to address Mediterraean salinity increase · Issue #127 · ACCESS-NRI/access-esm1.6-configs · GitHub
Forcings
GHG 0 Added to branch 7/5/25 Use CMIP7 GHG concentrations for PI control · Issue #110 · ACCESS-NRI/access-esm1.6-configs
Volcanic 0 Added to branch 14/5/25 Use CMIP7 volcanic forcing for PI control · Issue #114 · ACCESS-NRI/access-esm1.6-configs
Aerosols 0 Added to branch 6/6/25 Use CMIP7 aerosol emissions for PI control · Issue #123 · ACCESS-NRI/access-esm1.6-configs · GitHub
Ozone 0 Data not available yet
N dep 0 Data not available yet
Priority legend
0 Absolutely essential for production run in July
1 Would be great to have
2 In a perfect world

If the feature you wish to add doesn’t have a GitHub issue please create one and add it to the ESM1.6 project board. Instructions for doing this are here.

Got questions? Contentious things to discuss? Pop thoughts in this thread, below.

2

Shall we include the switch to OneAPI in that table?

3

Yes please. And any other known/planned optimisation changes.

1 Like
4

I’ve tried to group the table by changes that are more on the technical or I/O side, those that have a larger science component and those that are just on forcing. My thinking was that there is more potential to group some of the technical changes together when updating the configuration but the science changes may need to happen more incrementally.

5

I suggest we use the first hour of our regular NESP project meeting next Wednesday (4/6, 10am) to discuss the ‘science changes’ in the table. The aim would be to prioritise which changes go in when, dependencies between changes etc. If you aren’t already on the meeting invitation but would be interested in attending, please let me know.