Draft: Naming convention for CCPP suites

DRAFT Rules for Naming Suites

The CCPP Physics contains physical parameterizations, which are used by host models in suites. This page describes a proposal for naming convention of suites.

• Keep suite name as short strings, but have robust documentation about attributes (in CCPP scientific and Technical documentation)
• Specify host model, since at this time a suite needs minor differences to run in different hosts. E.g.,
  • UFS: FV3
  • CCPP Single-Column Model: SCM
• Avoid institution name to be more collaborative
• Clearly convey what is developmental, operational, and post-operational. Post-operational refers to a suite that is used in an operational model but whose content (that is, the actual physical parameterizations code) has marched ahead of what was used in operations. Use the following prefixes to denote the type of suite:
  • Developmental: dev
  • Operational: op
  • Post-operational: plus
• For UFS-related suites, clearly convey association of a suite with a particular UFS forecast application (if available)
  • If the suite is associated with a particular UFS forecast application
    • Use forecast application name and version in suite name (without underscore or hyphen between application name and application version). Use the Greek alphabet (alpha, beta, etc.) to indicate evolution, that is, how a developmental suite evolves before it is implemented.
  • Else
    • Use distinctive characteristic in suite name
  • Endif
• Additional decorators may be used to designate variations

FAQ

• When will these rules go into effect?

  TBD.

• What are some of the possible "additional decorators" mentioned in the rules?

  Possible decorators are coupled (to designate a variant for a coupled model), and ens (to designate an ensemble member)

• If this convention were applied to CCPP v6 (to be released in June 2022), what would the names of the supported suites be?

  The supported suites with the UFS are listed below. For the Single Column Model, SCM will be used instead of FV3.

  • Operational suites
    • None
  • Post-operational suites
    • FV3_plus_GFSv16: suite used in GFS v16 with schemes whose code has been advanced since operational implementation
  • Developmental suites
    • FV3_dev_GFSv17_alpha: developmental suite planned for GFS v17, first instantiation (alpha)
    • FV3_dev_GFSv17_coupled_alpha: developmental suite planned for GFS v17, first instantiation (alpha)
    • FV3_dev_RRFSv1_beta: developmental suite planned for RRFS v1, second instantiation (beta)
    • FV3_dev_WoFSv1_alpha: developmental suite planned for WoFS v1, first instantiation (alpha)
    • FV3_dev_HRRR: developmental suite analogous to the NOAA operational HRRR model
    • FV3_dev_RAP: developmental suite analogous to the NOAA operational RAP model

• What is the meaning of the acronyms used above?

  • UFS = Unified Forecast System
  • GFS = Global Forecast System (a NOAA UFS-based operational modeling system for medium-range weather forecasting)
  • RRFS = Rapid Refresh Forecast System (a NOAA UFS-based modeling system under development for short-range weather forecasting)
  • WoFS = Warn-on Forecasting System (a NOAA UFS-based modeling system under development for severe weather watches and warnings)
  • HRRR = High-Resolution Rapid Refresh (a NOAA operational modeling system for short-range weather forecasting)
  • RAP = Rapid Refresh (a NOAA operational modeling system for medium-range weather forecasting)
  • CCPP = Common Community Physics Package
  • SCM = CCPP Single Column Model