Meeting Summary
Meeting summary of the ACCESS-NRI internal meeting on 25/11/2025, on the managing and long term plans on the CM3/OM3/AM3 evaluation efforts.
Quick Recap
The team discussed integrating OM3, AM3 and CM3 evaluation workflows using a submodule approach, where OM3 and AM3 would be submodules in the CM3 repository. Ideally notebooks written for AM3/OM3 would also work on CM3, but not a trivial exercise.
Summary
OM3/AM3 as submodules in CM3 repository
- Plan is to make OM3 a submodule within the CM3 repository. Prevents desync of scripts between repositories.
- Where would AM3 sit in this? Worked well for OM3, as evaluation workflow was already in place, but AM3 does not yet have this community effort. Most likely, we would have atmosphere analysis contained in CM3 repo for now, and moved to AM3 repo when model is established.
- How to handle inconsistencies between CM and OM/AM? Apply pre-processing step, depending on which repo was running the analysis?
- This could be done by MOPPy, but this would be some time in future- MOPPy work focused on ESM1.6 currently.
OM3–CM3 Workflow Integration
- There are a number of issues which make generalisation of notebooks difficult- different variable names, time axes.
Maintenance
- How do we make it easy for users to test their scripts across models and configurations? It’s likely some work would fall to us, but ideally scripts would be quite general before being added to the repo.
AM3 / CM3 Meeting Integration
- Agreed to trial joint meetings with AM3 participants attending CM3 sessions.
- Considered structuring agendas so ocean discussion comes first, then atmosphere, so people can leave/show up when necessary.
Next Steps
-
AM3 Team
- How to put AM3 outputs in a format compatible with the intake catalogue?
- Invite 21st Century Weather team to CM3 evaluation meetings
-
OM3 Team
- Write a clear list of OM3/CM3 notebook generalization issues
- Use same variables for ocean outputs in OM3 and CM3 by using same diag table