ESM working group: Meeting notes 2024

Date: 09/10/2025
Chair: @tiloz
Participants: 14

Quick recap

The working group discussed changes to their meeting format and resources, including alternating between evaluation-focused sessions and broader topic discussions, while reminding participants about available computing power and storage allocations. The meeting focused on the CM3 model evaluation process, covering model development support and publication-focused evaluation phases, with discussions about GitHub repositories and analysis workflows. The group addressed meeting structure and naming changes, workflow contributions, and the importance of community involvement, while emphasizing the need for flexible participation options and clear communication channels.

Next steps

  • @cbull to share the GitHub repository link for CM3 analysis with the community
  • NRI team to set up automated figure generation and data storage for CM3 diagnostics
  • NRI team to consider implementing email notifications for new data releases
  • @ctychung to upload ENSO recipes to the GitHub repository
  • @cbull to show community members how to set up GitHub notifications
  • @MartinDix to reorganize coupled model meetings with a structured agenda and minutes
  • NRI team to consider setting up a SharePoint folder for publicly accessible figures
  • Community members to fill out the poll regarding potential changes to ESM Working Group meeting time
  • NRI team to provide a detailed walkthrough of the GitHub workflow at the next ESM Working Group meeting
  • NRI team to consider implementing a “watch” system for relevant Hive forum discussions to notify interested parties

Summary

Meeting Format and Resource Updates

The working group discussed changes to their meeting format, including potentially alternating meetings between evaluation-focused sessions and broader topic discussions, with a focus on including CM3 and ESM3 model evaluations.

They reminded participants about available resources, including 1.1 MSU of allocated computing power and 65 terabytes of storage, with guidelines available for accessing these resources. The group also encouraged members to submit work for presentation, particularly related to access models.

CM3 Model Evaluation Process

The meeting focused on the CM3 model evaluation process, which is divided into two phases: supporting model development through the rest of the year and into next year, and a later phase focused on evaluating a frozen model configuration for publication. A GitHub repository has been created for sharing analysis code and figures, while the ESM Working Group meetings will be used to discuss analysis results and address issues. The Ocean Team technical working group at NRI meets fortnightly and is open for anyone to attend and a similar invitation may follow (if there is interest) for the ACCESS-NRI CM3 dev meetings; most discussions will occur in the ESM Working Group meetings.

There was a kick-off CM3 evaluation group meeting the day before: see minutes on the forum.

CM3 Evaluation Repository Setup

The meeting discussed the setup of an evaluation repository for CM3, focusing on essential and bonus analysis. @cbull emphasized the importance of community expertise in enhancing model relevance and mentioned ongoing work to address data gaps. @wghuneke outlined the restructuring of ESM working group meetings, alternating between CM3 evaluation and science-focused discussions, and proposed a poll to determine a new meeting time. The group also discussed the need for technical input and the sharing of model outputs and GitHub repository information.

Refining ESM Meeting Structure

The meeting focused on the structure and naming of model development and evaluation meetings. @Dietmar_Dommenget suggested changing the name from “ESM Evaluation” to “ESM Development” to better reflect the collaborative nature of the process and encourage scientific involvement. @cbull and @MartinDix discussed the possibility of publishing meeting agendas and minutes to improve transparency and participation. @ongqingyee raised concerns about the time commitment required for CM3 output analysis, suggesting entraining more ECRs who are interested in CM3 development to participate. This would enable scientists with expertise but less time to still partake in technical discussion without having to do analysis themselves.

CM3/ESM3 Contribution Workflows Discussion

The meeting focused on discussing workflows and contributions for the CM3/ESM3 evaluation. @cbull explained that while GitHub is the primary platform for code sharing and analysis, there are flexible options for community members to contribute, including uploading figures without full code integration. The group discussed automation possibilities, with @Dietmar_Dommenget suggesting that diagnostic data should be stored alongside figures to enable further analysis, and @ctychung highlighting the need for clear communication about updates and notifications. The conversation ended with agreement that while GitHub and the Hive platform are valuable tools, there should also be options for verbal contributions and discussions during ESM working group meetings.

Additional information

These meetings notes were generated automatically. Please feel free to correct any mistakes in these notes directly, or message @Aidan with corrections.