ACCESS CM3 technical meeting minutes

Date: 5 Nov 2025

Continuing CM3 O025 run

Run with updated Baltic bathymetry (truncated OM3 file to avoid having to update model grid) and GC5 central atmospheric parameters restarted. Run shows a ~ 1.5 W/m^2 worsening of the net TOA radiation balance GC5 central configuration · Issue #53 · ACCESS-NRI/dev_coupling · GitHub. Possibly due to missing some GC5 central parameters that are not available in the standard vn13.0 code (Met Office used tests that made some internal parameters namelist variables).

TODO: Check whether this run did improve Baltic salinity drift and which components of the radiation balance changed.

Code version updates

ACCESS rAM3 uses UM vn13.5 and there’s now an update of both AM3 and CM3 to the same version. Runs ok but not fully tested yet. With this version we should be able to use the full set of GC5 central tunings.

TODO: @MartinDix to test GC5 parameters in AM3 AMIP experiments

Datastore:

@CharlesTurner’s work on zarr virtualisation has improved speed of reading atmospheric data enormously, though sea ice still seems slow. @anton suggests checking whether CM3 writes grid information every time (OM3 doesn’t). Virtualisation requires a higher level of file consistency and is not yet automated.

TODO: Look at creating catalog from model rose/cylc suite at end of each year. OM3 does this with a post-script triggered by payu om3-scripts/payu_config/postscript.sh at main · ACCESS-NRI/om3-scripts · GitHub. Would also require copying output to /g/data.

CM2 datastore

Question of which CM2 runs to use. Ideally use @wghuneke’s run but need to check where it started. 100 km ocean runs also worth adding (PI control will aready be in ESGF catalog but could add PD control).

@cbull to look at updating the evaluation template to include CM2 runs.

@MartinDix to create a list of key experiments like this OM3 list Experiments - ACCESS-OM3-configs