CSIRO - ACCESS-NRI standup minutes

24 March 2026

Paul, Anton, Jhan, Rachel, Spencer, Tilo, Claire, Josh, Martin, Siobhan, Pears, Dougie, Aidan, Lachlan

Runs

  • esm driven historical looks good (Atm CO2 looks good)
  • esm picontrol run > 600 years
  • runs paused (on P66) until new quarter
  • Min length for picontrol is 500 years, but generally aim for 1000 years

Nitrogen deposition

  • new version of forcing from upstream
  • Martin suggest we need consistent versions in PIControl and Historical
  • Inclined not to change this, but check for differences betwen old and new version first

Model documentation

  • Need to check on information on mass / velocity grids in ocean
  • Need DOIs for all references, Anton will email Elisabeth, Aidan will email Steve Griffies
  • Could make DOIs in ACCESS-NRI community with author support

Martin and Spencer have been looking at neaters ways to handle ensembles
Paul will look into scenario forcings soon

31 March 2026

Romain Anton Paul Dougie Martin Claire Spencer Lachlan Joshua Jhan Manodeep Aidan Rachel Tilo Matt Pearse Matt Siobhan Alex

Ocean diagnostics

  • Two core variables missing (2d daily surface salt and temperature)
  • Also a few other related changes

We save these monthly, and not super confident about use case for daily output

For the pi control - happy enough just to turn on from now

There are some idealised & historical runs which are already finished, these are possibly more relevant for reruns.

For now - well put the change in but not plan to re-run anything.

Atmosphere diagnostics

Some confusion about UM output having multiple time dimensions within one file. Are we saving instantaneous and average values correctly ?

Splitting into one file per variable seems like lots of work (this would be in post-processing). Some UM variables don’t have short names - so it’s hard to know what the naming scheme would be.
Spencer proposes splitting into one file for each time dimensions (as a simpler approach, possibly impacts UM output only ?)

Either approach, or the current output is probably ok for Moppy. So any changes are for future model users and to meet the access-nri data standard.

Josh and Spencer to spend some more time on post-processing (the work would be re-useable for AM3/ESM3) to meet access-nri data standard

Aidan wrote a tool called splitvar which may be a useful reference

CN and CNP

Happy to focus on CNP configs - we can archive CN configurations
It would be good if users / community can run in different modes
Some instructions for this could be good - one switch in UM namelist + some spinup

Payu clone

please test the interactive payu clone

module use /g/data/vk83/prerelease/modules/
module load payu/dev

Model registration

Rachel is progessing - slow on github reviews and unclear how to progress
Every grid + subgrid needs an issue and a review

Martin has piControl with v2 Nitrogen

will check results

7 April

Aidan, Anton, Paul, Jhan, Lachlan, Martin, Claire, Rachel, Dougie, Pearse

New control runs with time profiles updated

  • Restarted piControl+concentrations & emissions, from old year 200, and set back to 1. (So have upset the leap year sequenc)

  • Appears to have changed answers over restarts in piControl+emissions ?

  • Jhan to create an issue with exact configs compared

Some candidates:

  • possibly spack 0.22 to 1.1 wasn’t reproducible
  • check determinism over first 4 years - does this appear in 4th year? then it’s due to leap years

Nitrogen v2

No obvious impacts in Rachel’s analysis - we don’t know what we don’t know about it yet though (of course)

We like Nitrogen v1, but possibly this would be inconsistent with forcing in Scenarios - so as there apepars to be no impact, well update piControl+emissions to v2 (and all historical and all scenarios) - Does this make comparison between +emissions and +concentrations harder ?

Jhan will also start a parallel run with piControl+concentrations with Nitrogen v2 - spencer will make a restart for this.

Emissions driven historial

  • Trying to understant initial wood product pool size
  • There is some drift in CO2 in piControl, is this important for choosing start year for ensembles ?

Ensembles: - planned for 10-30 realisations of emissions-driven historical experiments and scenarios

Aidan stresses pushes payu runlogs to github.

See How to preserve reproducibility when applying perturbations in the event of a numerical instability crash - #8 by Aidan for committing when doing a pertubation.