# COSIMA TWG Meeting Minutes 2023

**URL:** <https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2023/399>\
**Category:** TWG\
**Tags:** meeting, twg, notes, minutes\
**Created:** [8 February 2023 01:36 UTC](https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2023/399 "2023-02-08T01:36:22Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![micael](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/micael/32/93_2.png) [@micael](https://forum.access-hive.org.au/u/micael)\
**Post date:** [17 August 2023 05:52 UTC](https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2023/399/11 "2023-08-17T05:52:59Z")

</div>

Notes from last week’s COSIMA TWG. Feel free to add whatever I’ve missed or to modify anything that I got wrong.

**Date** : 2023-08-09  
**Attendees** : Micael Oliveira @micael, Andrew Kiss @aekiss, Aidan Heerdegen @Aidan, Paul Leopardi @paulleopardi, Dougie Squire @dougiesquire, Rui Yang @rui.yang, Angus Gibson @angus-g, Harshula Jayasuriya @Harshula, Ezhil Kannadasan @ezhilsabareesh8, Siobhan O’Farrell @sofarrell

**MOM6 Test Cases**

- Call is out for MOM6 test cases (see [A call for community model configurations that use MOM6](https://forum.access-hive.org.au/t/a-call-for-community-model-configurations-that-use-mom6/1049))
- Question about how to do run the tests in practice from a technical point of view (see [Technical requirements for MOM6 node testing](https://forum.access-hive.org.au/t/technical-requirements-for-mom6-node-testing/1052)):
  - How to launch test on gadi now that access-dev is going to be decommissioned? Should we use github actions?
  - ACCESS-NRI is working on setting up CI infrastructure (VM on Nirin running github runners)
  - Tests can be set up while waiting for infrastructure. Start with one test (e.g., Panan) to work out process.
  - Should tests go to a git repository, just like mom6-examples? Too much maintenance?
    - Depends on how similar tests are to production. Should be fairly close, so production configs get tested.
    - Maybe we could patch production configs for tests - eg shorter run, fewer diagnostics
    - We should use Payu. NRI needs to be broader, since other models use rose/cylc.

  - How to deal with cases that aren’t bitwise reproducible, but close enough? We can start with manual checks. MOM6 PR’s usually have notes as to whether bitwise reproducibility is expected
  - MOM consortium requires nomination of someone to sign off on tests. Suggestion for Angus to do it, plus someone else as backup.

**ACCESS-OM3 Status**

- Setting up new configuration to be close to OM2
  - grids etc done, JRA55-do done, separate PRs, need to merge once crash is fixed; parameter settings still need attention.

- Ongoing comparison of ACCESS-OM3 and CIME builds. Still some differences in results, but closing in. Checking compiler flags, including for dependencies.
- Found mismatched constants between model components
  - defaults in code; can be overridden via input at runtime
  - see what parameters CIME fixes

- Will tag configurations and executables matching CIME builds as a starting point, and have history for reproducibility.
- Shioban noted that CICE6-WW3 configuration doesn’t run properly because DOCN needs to supply additional fields, and NUOPC cap for CICE6 needs options to pick up ocean currents from DOCN.

**ACCESS-OM3 Release Process**

- A release of ACCESS-OM3 should include all the things needed to reproduce a given run: codebase, spack env, configs, inputs.
- We would like to have the same version number in all tags
- Open questions:
  - how to version the inputs?
  - how about CI docker images - tag those?

- ACCESS-NRI release team working on these issues.
  - If NRI does releases, NRI will take responsibility for tests, updates to software stack
  - OM3 can be a test case to see what works

---

_[View the full topic](https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2023/399)._