CCPP Framework Meeting Minutes 2021 10 21

• Transition to capgen.py
• Dictionary of standard names

---

Transition to capgen.py

• Estimates of dedicated time needed to complete unification tasks added to GitHub issues
  • https://docs.google.com/spreadsheets/d/1u_yA9PyG9aVHMvlXDjmVIaxcgaKo2nR7NPVV2Kmw0Ck/edit#gid=0
• Could use help to write unit tests that will pass once new capgen features are implemented (e.g., blocked data, unit conversion)

Dropping support for optional arguments

• Use flags to determine which branch to take in the code and whether to access certain variables (can be optional), instead of testing for presence
• Together with the active attribute and the extended usage of present in the Fortran 2008 standard, we do not need the optional attribute in the CCPP metadata

Dictionary of standard names

• Need interoperability standard_names clearly separated from host-model specific standard_names
• Steve was asked to create a more focused version of the dictionary for interoperable standard names, because the full dictionary with all UFS standard names is too complex
  • We need to make sure that Steve's efforts are translated into a permanent solution, for example by adding host model qualifiers to standard names
  • Once still has gathered enough experience with the process, he will report back
• Once matured, we need to share this dictionary with the CCPP physics governance group to gain visibility

Other business

• We need a process to update the CCPP requirements (e.g. optional arguments, single precision, ...)
  • Does this committee have the authority?
  • Who should be involved to provide input, feedback, ...
  • CCPP physics governance group must be included (scheme point of contacts / codeowners)
  • In kind contributors should also have the right to comment on requirements, not only the funding agencies
• We need a procedure with established timelines