Hi Everyone,
We’ve been working with the output from the ACCESS-ESM1.6 piControl spin-up run, available at:
/scratch/p66/pjb581/access-esm/archive/pi_concentrations-expt-c55f7217
There’s been ongoing discussion around evaluating these outputs using ILAMB and ESMValTool. @RhaegarZeng is currently preparing an ILAMB workflow to process and assess the data.
In parallel, I’ve been developing a lightweight version of MOPPeR designed for use within a Python/Jupyter environment on ARE, compatible with tools like ESMValTool. It’s still in early development (v2.0.0-alpha0), and available here:
GitHub - ACCESS-NRI/ACCESS-MOPPeR: ACCESS-MOPPeR
As expected, there are still uncertainties around the output conventions—for example, final file structure, naming, and how many variables appear per file. The atmospheric data appears relatively straightforward (aside from a few missing variables—see below), but the ocean and sea-ice components remain more complicated due to the CMOR requirement to define grid cell bounds. I’m currently using the supergrid definition (thanks to @dougiesquire for flagging that), but ideally, this info would be embedded in the ESM1.6 output or linked via a unique grid identifier @Aidan.
STASH to CMIP Mapping
To progress the CMORisation workflow, we need a robust mapping from ACCESS-ESM1.6 STASH codes to CMIP variable names. So far, I’ve been referencing outputs from APP4 and MOPPeR v1 (developed for ACCESS-ESM1.5), but it looks like some STASH codes and output variable definitions have changed in ESM1.6.
I’ve put together a working spreadsheet listing the core variables needed for a baseline CMIP submission (i.e. the minimum required for FastTrack):
ESM1-6_CMIP7_Mapping.xlsx - Google Sheets
If you or your team could help review and update the mapping or calculations, that would be very helpful.
For reference, the mappings currently used by MOPPeR v2.0.0-alpha0 are here:
ACCESS-MOPPeR/src/access_mopper/mappings at v2 · ACCESS-NRI/ACCESS-MOPPeR · GitHub
Clear documentation of ACCESS-ESM1.6 outputs is becoming urgent—both for evaluation purposes and to support CMIP submission. Any input, corrections, or suggestions from the community would be greatly appreciated! @ClareCR
@clairecarouge @cbull @heidi @Aidan @ClareCR @inh599 @RachelLaw @tiloz @arnoldsu @anton @anton @MartinDix @kdruken
Thanks all!