CCPP Framework Meeting Minutes 2021 06 08

Agenda

PR "Updated CCPP standard names": https://github.com/ESCOMP/CCPPStandardNames/pull/13
PR "Rules for creating CCPP standard names": https://github.com/ESCOMP/CCPPStandardNames/pull/14
What is the purpose and the scope of the CCPP standard names dictionary?
Dictionary is a lookup resource, not used actively during build
- Add a statement at the top of the repository to make this clear
- For interoperability, not for functionality
- Can add a lint tool to verify standard names against it
- Should it contain units?
  - If so, which? Defaults? All supported units?
  - Jimy: units can help to identify "wrong" standard names (e.g. heat flux vs potential temperature flux), useful
What about lumped chemical species?
- The standard name won't change, can the long name be used to describe that X consists of A+B+C here, but only A+B somewhere else?
Andrew will create a PR for the standard name repo with a short statement what the dictionary means for chemistry

Revisiting the old topic. Could the framework substitute horizontal dimensions behind the scenes, so that scheme developers don't have to worry about it?
- See https://github.com/NCAR/ccpp-doc/pull/45
- Best to maintain the explicit distinction and educate developers
For debugging, it would be useful to have a standardized way to pass information on global indices and location to the physics
- What would be good standard names for these variables?
- Different models have different requirements (global vs regional, regular grid vs unstructured meshes vs ...)

CCPP Framework wiki