-
Notifications
You must be signed in to change notification settings - Fork 64
CCPP Framework Meeting Minutes 2020 10 20
Dom Heinzeller edited this page Oct 20, 2020
·
2 revisions
- update on transition to cap_gen.py
- update on MPAS-CCPP work
- other business
- first bunch of changes merged into master (cleanup/consistency of metadata entries, units, removal of GFS DDTs from radiation)
- report on consolidation of standard names:
- proposed rules to compose standard names (extending CF conventions)
- about 3/4 of existing standard names checked
- soon-to-be-shared google doc with proposed rules and suggested names for existing variables for discussion; who should be there?
- we are about one month behind schedule, hopefully still on target to transition before the end of the year
- current clean up work in the UFS (removal of gnumake build, removal of IPD) will make the transition to
cap_gen.py
easier
- MPAS close to running CCPP physics (hardcoded in driver, a bit like the hybrid CCPP in the UFS in the past) in the 2nd week of November
- Q1/2021: milestone for running one physics suite in MPAS
- Q3/2021: milestone for running one physics suite in MPAS in the "proper" CCPP way
- standard names:
- MMM (Dave) has his own list standard names
- work with Grant and Ligia to converge to one set of rules and list of standard names
- when CCPP physics governance is established, hand off the unified standard names dictionary/rules to them
- discussion with EPA on using CCPP for chemistry and physics (Georg and Dom)
- EPA will also want to run additional physics in MPAS and is willing to port them (starting with ACM2)
- Judith Berner is interested in running MPAS physics in SCM; Dave and Grant will work on this
- MMM wants to run MPAS chemistry through CCPP; Dave to chat with Georg (Grell) about using the GSL CCPP chemistry routines
- Optional arguments in CCPP:
- https://github.com/NCAR/ccpp-framework/issues/305
- probably ok (Dave to check) to not use optional arguments at all in CCPP and rely on "active attribute"
- Issue with latest (?) version of Intel compiler when passing an allocatable array as intent(in) to a subroutine: crashing when not allocated, even though array declared as assumed-size array
- Steve to share a small reproducer code with Dom
- Dom to discuss with Intel developers on Friday