CCPP Framework Meeting Minutes 2020 11 17

Agenda

• cap_gen.py progress
• transition to cap_gen.py
• NOAA / NCAR-ACOM model development
• other business

cap_gen.py progress

• Steve is making progress, working on build issues (compile all suites if none specified; can use wildcards etc.)
• need to talk about how to implement the unit conversion in cap_gen.py
• October 6 meetings notes list all issues that need to be addressed - add label to issues to identify

Transition to cap_gen.py

• Updated 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)
• Follow up on discussion of last week on removal of optional arguments (or not)
  • From two weeks ago: Do we need consent from developers to not support optional arguments? Do we tell developers to not use them right away? Do they need alternatives? Whom to contact? EMC, GSL, Robert & Dustin
  • Dom will do
• timestep_init, timestep_finalize - issue with too long subroutine names in Fortran
  • internally use tsinit and tsfinal for ccpp_prebuild.py
  • happens frequently with SCM, but only created warnings not errors - different compiler (GNU vs Intel)? 39 | function FV3_GFS_2017_gfdlmp_regional_c768_fast_physics_timestep_init_cap() result(ierr) | 1 Error: Name at (1) is too long
  • we could set limits of 15 or 20 characters for the suite name, and similar for the group name
    • truncate using some logic, and then put the full name in a comment
    • recommend users to use shorter names for suites and groups to avoid having their cap names truncated
• Consolidation of standard names (Ligia and Grant) - https://docs.google.com/spreadsheets/d/1kWDC7_2sagm-PTP_tXaGyI3O3sJFK8FY9FElQbb6V3o/edit#gid=613941307

NOAA / NCAR-ACOM model development

• ...

Other business

• ...