CCPP Framework Meeting Minutes 2024 02 26

Agenda

• GitHub issues/PRs
• New items
• Updates
• Other business
• notes

---

Attendees: Mike Kavulich,

First item: need a note-taker

• Not a permanent position, can rotate

GitHub issues/PRs

CCPP Framework (issues, PRs, discussions)

• PR 523: Add support to use mpi_f08 MPI module
  • Looks like consensus is to make mpi_f08 required for CCPP
• Issue 527: Create tests for Optional attribute
  • Is this capgen only?
• PR 533: Clean up/fix ccpp_prebuild CI tests
  • Merged, should see no more failing CI tests in framework repo
• Need PR for https://github.com/climbfuji/ccpp-framework/tree/feature/dummy_allocate_inactive
  • Part of the conditionally-allocated array PRs for -check all NCO requirement (https://github.com/NOAA-EMC/fv3atm/pull/767)

Standard names (issues, PRs, discussions)

• PR 56: Add new standard names from NCAR idealized physics schemes
  • Needs approval from Grant
• Issue 57: Feedback on the meaning of: sea_ice_area_fraction_of_sea_area_fraction
  • Some proposal for standard name change

New items for discussion

Standard names

• Should units control what kind of mixing ratio (volume, mass, number concentration) it is as opposed to the standard name?
• How should moist/dry/wet mixing ratio property be set? How can we make sure this works properly with variable standard names? Currently this property is set based off the standard name itself, although the actual names being used are out-of-date: https://github.com/peverwhee/ccpp-framework/blob/add_const_interface/src/ccpp_constituent_prop_mod.F90#L421
• Should moist/dry/wet be controlled by standard name, or by metadata property [like "advected"] (which the constituents property object is carrying around anyways)? Also should there not be a default value (to make sure the property is always set)?
• What units do we want to support for unit conversion?

CCPP version 7 release

• CCPP stand-alone v7 release planned for ~June 2024
• Any specific changes that we'd like to target prior to this release?

Timelines for PR reviews

• 1 week from initial review, code manager will send out reminder
• Ways to track review requests centrally?
  • SRW uses a GitHub project: https://github.com/orgs/ufs-community/projects/38/views/1

Updates from last time

Previous notes

Other business

Meeting notes