ACCESS-OM3 architecture
The schematic below illustrates the structure of the MOM6-CICE6-WW3 ACCESS-OM3 executable. ACCESS-OM3 is a single executable, consisting of the NUOPC driver (the main program) and several model components, each wrapped in a NUOPC cap; the caps are coupled through the CMEPS mediator via NUOPC connectors. NUOPC is an interoperability layer for ESMF which standardises how model components interact. See discussions here and here for more information.
The coupled fields and remapping methods used are recorded in the mediator log output file and can be found with grep '^ mapping' archive/output000/log/med.log; see here for how to decode this. See the Configurations Overview page for details on how the coupling is determined.
Overview of codebase
The ACCESS-OM3 software is built from libraries containing the code for each model component.
The top level code (main program) for an ACCESS-OM3 executable is the CMEPS NUOPC driver CMEPS/CMEPS/cesm/driver/esmApp.F90.
The software deployment compiles a single executable for the model. Each single exectuable contains the driver, CMEPS NUOPC mediator and different selections of these model components:
- ocean: MOM6 active model or DOCN prescribed data model from CDEPS or nothing (stub)
- sea ice: CICE6 active model or DICE prescribed data model from CDEPS or nothing (stub)
- waves: WW3 active model or DWAV prescribed data model or nothing (stub)
- atmosphere: DATM prescribed data model from CDEPS
- runoff: DROF prescribed data model from CDEPS
The default deployment contains two builds, the access-OM3-MOM6-CICE6 executable contains the active ocean and sea ice model and no waves, and the access-OM3-MOM6-CICE6-WW3 executable contains the active ocean, seaice and wave models. Other combinations of prescribed and active model components are possible but not probided by default.
The model components are coupled exclusively through the mediator via their NUOPC caps: MOM6, CICE6, WW3, DOCN, DICE, DATM and DROF.