CCPP Framework Meeting Minutes 2020 07 16

Agenda

dependencies of CCPP schemes on other Fortran modules (see https://github.com/NCAR/ccpp-framework/issues/308)
active attribute
horizontal dimensions
other business

see https://github.com/NCAR/ccpp-framework/issues/308
filenames are used by most build systems
if a build system needs module names, the framework could get them from the filenames
add a new metadata section for the scheme as a whole, i.e. "above" the _run etc. routines
- can infer that this is a valid "scheme name" by parsing the _xyz scheme names (cap_gen.py)
- ccpp_prebuild.py comes from Fortran and knows the scheme name before parsing the metadata file
- call it [ccpp-scheme-properties] instead of [ccpp-arg-table]?
- what else can go into the scheme properties section? (brain storming)
  - is a scheme used by a certain host model
  - is a scheme active or not (depending on a standard name)
  - process identifier
  - does a scheme want to be time split or process split - or is that a suite designer's choice?
  - compiler flags - or is that something that belongs to the host model's build system?

the current implementation of the active attribute (see https://github.com/NOAA-EMC/fv3atm/blob/develop/gfsphysics/GFS_layer/GFS_typedefs.meta) makes sense, so we will expand this to all fields that need this attribute

hide the "complexity" of horizontal_dimension versus horizontal_loop_extent or be explicit as possible and educate the users?
best to be explicit as possible and educate the users; will need to make the corresponding change in all metadata files of gmtb-scm, fv3atm and ccpp-physics in isolated commits and create some documentation for users (maybe a tutorial as well)?

CCPP Framework wiki