CCPP Framework Meeting Minutes 2024 10 03

Agenda

Attendees: Michael Waxmonsky, Jesse Nusbaumer, Dustin Swales, Jordan Powers, RhaeSung Kim, Cheryl Craig, Dom Heinzeller, Courtney Peverley

CCPP Framework

Equivalent units (#571)
- No updates
Register (#582)
- Courtney to finish testing; open to review
Tendency capability (#584)
- Dustin left a comment for Courtney to address - use existing infrastructure for variable compatibility
Full error message from xmllint (#586)
- Approved - good to go; Dom merged
DDT host object test (#591)
- Steve added new test; has started conversation about testing strategy (unit tests vs system tests?)
- Dom - we need to at least document what is tested in each larger system test
- Dom - next step could be a template suite/scheme that could be build up for smaller tests
- Michael - suggests pfunit for testing - needs further discussion
  - Example of use of pfunit testing that Michael set up for part of CAM-SIMA: https://github.com/peverwhee/history_output/pull/1
  - Dom has a contact within pfunit team
  - Mock object example - https://google.github.io/googletest/reference/mocking.html
Constituents object uses wrong standard name
- Courtney to fix in upcoming constituents bugfix PR
Debug checks output unreadable writes (#590)
- Debug tests - needs update; should be straight-forward
Fortran parsing error (#593)
- Steve looking into this
Unit conversions in two schemes (#594)
- Dustin thinks this is related to an optional argument bug he fixed - has a fix in mind
- Also seems to be an issue in prebuild based on Courtney’s testing
  - Dom to look into it

Standard Names

Dom merged PRs from JCSDA
- No open PRs right now
- We need to try to expedite the review process
Dom: We’ve updated the rules a couple times, but we haven’t fixed the standard names in the dictionary to adhere to the rules
Usage of standard names outside of metadata
- ESMF - uses field dictionary; names in yaml files
  - Every modeling system has its own dictionary; UFS will make a push to use CCPP standard names
Jesse - do we need to discuss the current structure of the repo? Subsections? Organize by type of variable instead of data structure?
- Dom - we will also need tagging so updating doesn’t have to happen as often
  - A “bonus” meeting at a different time that includes more stakeholders to discuss versioning may be in order
    - Dom to coordinate a time

Discussion

CCPP Framework wiki