CCPP Framework Meeting Minutes 2020 04 02

Agenda

• Discussion with NRL team
• Proposal Add suite keyword to suite definition file? https://github.com/NCAR/ccpp-framework/issues/275

"Tour de cap_gen.py"

• introduction of a post-analysis database dump
  • database contains a lot of information about the run
  • from the command line, via a Python interface, or via a new inspection routine
• what is needed to transition GFS physics to cap_gen.py
  • handle blocked data structures for the different stages (init, run, ...)
  • GFS data types
  • stricter requirements in cap_gen.py (order of arguments, compare Fortran code and metadata, horizontal_dimension versus horizontal_loop_extent)
• additional features to be developed in the near future
  • advanced diagnostics (accumulating, averaging, ...)
• CCPP physics schemes are usable by both ccpp_prebuild.py and cap_gen.py as-is (but cap_gen.py is stricter checking for the requirements, see above)

Proposal Add suite keyword to suite definition file? https://github.com/NCAR/ccpp-framework/issues/275

• will it make it easier or create problems elsewhere
• Dom's opinion is to keep cap_gen.py as easy as possible - is this a tradeoff to holding back good development? Please think about it and comment on the issue

Collaboration with NRL on SCM and on GPU/NUOPC caps

• three areas identified for collaboration: variable information exchange between CCPP and host model, SCM, rejected GPU-NUOPC cap proposal
• best way to go forward: transfer funds from NRL to NCAR, or assist development at NRL?
• implementing another vertical advection scheme (spectral element vertical advection scheme) in SCM should be relatively straightforward; NRL would like to get started on this at some point this quarter (Q2/2020)
• GPU-NUOPC cap SIP proposal
  • NEPTUNE will be GPU enabled in the future, MPAS already is
  • John's work on coordinate-independent code