Scheduled Maintenance - June 4

  • We will be undergoing some maintenance to our website on Thursday, June 4, around 11 am MST.  Our site will be unavailable for a period of time while we are making a web server change.
  • Sorry for the inconvenience. We’ll be back up and running as fast as possible.

Common Community Physics Package (CCPP) | System Architecture

There are two distinct parts to the CCPP: a library of physical parameterizations (CCPP-Physics) that conforms to selected standards and an infrastructure (CCPP-Framework) that enables connecting the physics to a host model.

CCPP Architecture
 Architecture of the CCPP and its connection to a host model, represented here as the driver for an atmospheric model (yellow box). The dynamical core (dycore), physics, and other aspects of the model (such as coupling) are connected to the driving host through the pool of physics caps. The CCPP-Physics is denoted by the gray box at the bottom of the physics, and encompasses the parameterizations, which are accompanied by physics caps.


The host model needs to have functional documentation for any variable that will be passed to or received from the physics. The CCPP-framework is used to compare the variables requested by each physical parameterization against those provided by the host model, and to check whether they are available, otherwise an error will be issued. This process serves to expose the variables passed between physics and dynamics, and to clarify how information is exchanged among parameterizations. During runtime, the CCPP-Framework is responsible for communicating the necessary variables between the host model and the parameterizations.