Skip to content

CCPP Framework Meeting Minutes 2020 06 11

Dom Heinzeller edited this page Jun 11, 2020 · 6 revisions

Agenda

  • multiple versions of physics schemes
  • follow-up on active attribute, optional arguments
  • discuss/explain the slide on suite definition files from Dave's talk at WRF/MPAS workshop

Slide on suite definition files from Dave's talk at WRF/MPAS workshop

  • this is issue https://github.com/NCAR/ccpp-framework/issues/275
  • building blocks to construct suites from groups that are usually run together
  • use include statement in the suite definition file that uses the group
  • from Steve: scientists are excited about this idea
  • has not been implemented yet (Dave's talk conveyed that differently), it will be several months before this gets implemented
  • cap_gen.py will print out the suite as analyzed (i.e. synthesized), and also as part of the debug prints

Multiple versions of physics schemes

  • MMM made a lot of progress on CCPP-izing some of their physics
  • overlap with physics that we have already
  • there is no plan to use the same physics, i.e. truly achieve interoperability
  • need to reassemble a group to talk about a shared physics repository, set up experiments where we use each other's physics
  • circling back to the required and still-missing multi-institution governance of physics
  • Example: pumas microphysics as a successor for MG (and possibly Thompson); effort to run CCPP-ized MPAS physics in CAM
  • NCAR has an ongoing and funded project to work on interoperability for physics, it is not clear how much funding (and willingness) we have on the NOAA side
  • Can we start this off using YSU or Thompson MP as an example?
    • the ccpp-physics version is very close to WRF v4.1.0
    • it is not used in operations by NOAA (yet) and not one of the primary schemes for the MPAS-WRF CCPP effort
    • use a different GitHub space for such shared physics
  • RRTMG unification efforts - longer term project
  • Dom to post links/filenames of versions of physics (e.g. Thompson, YSU)

Follow-up on active attribute, optional arguments

  • optional arguments are difficult to implement
  • other options are #ifdef etc - "ugly" code?
Clone this wiki locally