CCPP Framework Meeting Minutes 2020 08 06

Agenda

• transition to cap_gen.py
• NRL collaboration
• ccpp-standalone
• other business

Transition to cap_gen.py

• DTC timeline and resource chart (https://docs.google.com/spreadsheets/d/1XbSF1ejYcPMrVtZtk1OSiMX-vI5srLkwEUhyAirGr8k/edit?usp=sharing)
• things that need to happen for transitioning UFS to cap_gen.py (https://docs.google.com/document/d/1M3mCO3ESR9OJqLyUbQf-ahJtmfmGKilZlWaBTxsfMRk/edit?usp=sharing)
• CCPP dependencies
  • PRs for ccpp_prebuild.py: https://github.com/ufs-community/ufs-weather-model/pull/180
  • issues: https://github.com/NCAR/ccpp-framework/issues/308 and https://github.com/NCAR/ccpp-framework/issues/318
  • a more generic implementation that adds the [ccpp-table-properties] section for module, ddt and scheme tables is preferred
  • can specify dependencies on multiple lines
  • can have a relative_path attribute
  • [ccpp-table-properties] mandatory for each module/DDT/scheme
  • this generic section opens possibilities for future development, e.g. dependencies of primary schemes on interstitial schemes; possibly in combination with a [ccpp-host-info]/[ccpp-host-properties] section for host-specific insterstitials?

NRL collaboration

• Alex and Matus currently updating to latest ccpp_prebuild.py in NCAR master
• potential issue with module level data used in the auto-generated static API
• this won't be an issue with cap_gen.py, where the argument list passed to the static API is generated at compile time (while it is static in ccpp_prebuild.py)

ccpp-standalone

• Should we create a ccpp-standalone repository that contains a toy model to drive (and test!) ccpp-framework and ccpp-physics?
• Better to add a testing harness (dummy host model) to ccpp-framework, see https://github.com/NCAR/ccpp-framework/issues/319