Home
Welcome to the documentation for the ACCESS-OM3 ocean-seaice model configurations!
ACCESS-OM3 is the third generation of the ACCESS global ocean - sea ice model. It uses up-to-date releases of the MOM6 ocean model and CICE6 sea ice model. It is the first ACCESS model that couples model components using CMEPS (Community Mediator for Earth Prediction Systems), built on top of NUOPC (National Unified Operational Prediction Capability) infrastructure.
ACCESS-OM3 Quickstart
If you would like to simply run the model, see the How to Run ACCESS OM3 documentation.
ACCESS-OM3 Documentation Overview
See the navigation links on the left. Some reading tips, see:
- Contributing if you'd like to get involved / provide feedback on ACCESS-OM3;
- Inputs if you would like to understand how the input files are generated;
- Configuration choices/Configurations for information/background about specific configurations. The remaining sub-sections in
Configuration choices
provide background on key files and background on how ACCESS-OM3 configurations work/can be customised. These parts are likely of most interest to users. - Infrastructure is likely of more interest to ACCESS-NRI staff and developers. Having said this, some users, might find pages such as
Architecture
useful background.
ACCESS-OM3-Configs Overview
ACCESS-OM3 configurations are provided via branches in the access-om3-configs GitHub repository. The access-om3-configs repository contains several configurations using the following components:
- MOM6 ocean model
- CICE sea ice model
- WW3 wave model
- DATM atmosphere data model
- DROF runoff data model
All the configurations use the Payu workflow management tool, and pre-built executables available on NCI.
Repository structure
The main
branch does not store any model configurations, only documentation.
Each configuration in github.com/ACCESS-NRI/access-om3-configs repository is stored as a git branch. Most of the branches are named according to the following naming scheme:
{dev|release}-{MODEL_COMPONENTS}_{nominal_resolution}km_{forcing_data}_{forcing_method}[+{modifier}]
where {MODEL_COMPONENTS}
is an acronym specifying the active model components in the following order:
M
: MOM6C
: CICE6W
: WW3r
: a regional configuration
and the nominal resolution is given in kilometers, corresponding to the nominal resolution in degrees as follows:
100km
: 1°25km
: 0.25°10km
: 0.1°8km
: 1/12°
For regional configurations, a short word describing the location of the domain is included after the nominal resolution. For example:
tas5km
: 5km resolution around Tasmainiasuperoz4km
4km resolution around Australia
Additional configuration information, like if the configuration includes biogeochemistry, is appended to the name as a modifier, e.g.
+wombatlite
if the configuration uses WOMBATlite
Currently the following released configurations are available:
Currently the following development configurations are available:
MOM6-CICE6-DATM-DROF configurations
dev-MC_100km_jra_ryf
dev-MC_100km_jra_iaf
dev-MC_100km_jra_ryf+wombatlite
dev-MC_25km_jra_ryf
dev-MC_25km_jra_ryf+wombatlite
MOM6-CICE6-WW3-DATM-DROF configurations
Warning
These dev_*
configurations are still under development and should not be used for production runs.
Comparison table
The following links can be used to easily compare different configuration branches
MC → MC
release-MC_25km_jra_ryf
⬅️dev-MC_25km_jra_iaf
dev-MC_100km_jra_ryf
⬅️dev-MC_100km_jra_iaf
dev-MC_100km_jra_ryf
⬅️dev-MC_100km_jra_ryf+wombatlite
dev-MC_100km_jra_ryf
⬅️dev-MC_25km_jra_ryf
dev-MC_100km_jra_ryf+wombatlite
⬅️dev-MC_25km_jra_ryf+wombatlite
dev-MC_25km_jra_ryf
⬅️dev-MC_25km_jra_ryf+wombatlite
MCW → MCW
MC → MCW