Meeting minutes
Date: March 4th 2025
@Jhan, @cbull, @harshula, @manodeep, @RachelLaw, @MartinDix, @tiloz, @micael, @anton, @spencerwong, @paulleopardi, @inh599, @clairecarouge, @ben, @Aidan, @dougiesquire
Agenda Items
- Chris Bull no pre-existing agenda items.
Communication Update
- Claire Carouge highlighted the move of our ESM1.6 communications from a hidden message to a public topic.
- Chris Bull clarified the renaming of the thread and encouraged attendees to watch the thread for notifications (click bell down the bottom).
Project Board Review
- Chris Bull reviewed the ESM 1.6 project board and invited attendees to mention any blockers or issues.
- No issues / blockers were mentioned.
Experiment Documentation
- Chris Bull emphasized the importance of documenting experiments, especially those used for production runs in July. This process has begun already, thanks @spencerwong and @pearseb
- Spencer Wong discussed the creation of a GitHub repository for experiment details and provided instructions for pushing experiment branches.
- Specifically this branch naming convention
<GH-user-name>-<dev/test>-<YYYYMMDD>-<counter>
and the use of GH issues for any descriptors. Please see README for further instructions. - @pearseb not here today but please add experiment for current spin up experiments to this repo’.
- Note this is a different GH organisation so you’ll need to get in touch with @clairecarouge / @spencerwong to get access.
General Matters
- Claire Carouge raised an issue about building and running ESM 1.6, mentioning a runtime error related to generic tracers.
- Dougie Squire and Harshula discussed potential issues with the build system and configurations and the need for updates on both.
- Dougie Squire wanted to know which config branch to focus on, this one
Data Management Plan
- Ian raised a concern about data storage and the potential for data purging on scratch storage.
- Rachel Law and Tilo Ziehn discussed the need for a data management plan, especially for spin-up and production runs. Only a subset is probably practical to keep on disk the rest can go on tape.
- Paul Leopardi requested a copy of Chloe’s original data plan for reference.
- No one is currently assigned to write a Data Management Plan (afterthought: @cbull will ask @ClareCR about next steps?)
- @Aidan payu has in-built sync support. If we’re in danger of losing important information it should be turned on
Compiler and MPI Updates
- Harshula expressed the need to use a newer compiler and OpenMPI version for future test runs. Namely openmpi: 4.1.5 / ifort: 2021.10.0. See PR. When is the best time to roll out these changes?
- No one followed up at standup. Chris would follow up offline.
Action Items
Chris Bull to follow up on the sequencing of changes related to the new compiler and MPI version.Rachel Law to provide Paul Leopardi with a copy of Chloe’s data plan.- Dougie Squire to review and update ESM1.6 configuration to ensure compatibility.
Closing Remarks
- Dougie Squire Looks like I won’t have time to raise my hand. I want to update the ocean grid, which will also entail updating the ice grid and remapping weights: link
- Chris Bull Out of time today, please send agenda items in advance such that we can plan for time as appropriate
- Chris Bull thanked attendees and closed the meeting. @clairecarouge is hosting next week.