CCPP Framework Meeting Minutes 2019 09 26

Updates:

All ccpp-physics, FV3 and SCM are using the new metadata format
NEPTUNE will follow when updating their one-year old ccpp-framework/physics code

EMC was also asking about how we test CCPP outside FV3
Steve has some tests - definitely more than the unit tests that ccpp-framework has now
Incremental testing needed: unit testing, testing with physics, test on multiple platforms / with multiple compilers
Current Travis tests are for validating XML files and test basic functionality with the dynamic build
Can use Python testing framework
Use Pylint (with exceptions)?
Can we test the existing system tests for capgen with ccpp_prebuild? Does it make sense? Is there additional functionality needed?

create a branch in NCAR ccpp-framework: feature/capgen
improve/add tests on this branch, don't worry about ccpp_prebuild.py
side note: need to transition to Python 3 asap - Python 2 will be history by end of 2020; need to take into account how quickly EMC, NCO, NRL etc. will be moving over
we will try to avoid sixt.py - test Python version using try: ... except: ... to figure it out
make capgen compatible with Python 2 & 3 by end of December 2019, don't worry about ccpp_prebuild
toy host model used now for testing in capgen uses patterned arrays to give hints on where something might have gone wrong
Use GMTB SCM has another host model for testing, similar to the NEMSfv3gfs test? But these tests are run anyway as part of the host model regression tests

need gmtb/develop and master branches for ccpp-doc
tag future releases (for older releases can use tag in ccpp-framework)
need to have latest documentation for both master and gmtb/develop online
Use GitHub functionality github.io? Better use pointers from DTC website for all branches that we document: latest release, master, gmtb/develop, ...

CCPP Framework wiki