ACCESS-CM2 (ACCESS Coupled Model 2) is a global fully-coupled climate model that includes the atmosphere, ocean and sea-ice components, and produces physical climate simulations. ACCESS-CM2 is one of the two models run by the Australian climate community for the
@@ -28,7 +28,7 @@ ACCESS-CM2 (ACCESS Coupled Model 2) is a global fully-coupled climate model that
ACCESS-NRI will release an ACCESS-CM model configuration. The first release of ACCESS-CM will be derived from the [CSIRO ACCESS-CM2 configuration](#access-cm2) and will include [atmosphere], [land], [ocean] and [sea ice] components.
-##
[ACCESS-CM2] {{ recommended }}
+##
[ACCESS-CM2]
[**Citation** [@Bi2020-vj]][ACCESS-CM2-cite] |
[**Tutorial**][ACCESS-CM2-tute]
diff --git a/docs/models/configurations/access-esm.md b/docs/models/configurations/access-esm.md
index 762cc1916..0df7c11a8 100644
--- a/docs/models/configurations/access-esm.md
+++ b/docs/models/configurations/access-esm.md
@@ -1,4 +1,4 @@
-#
ACCESS-ESM {{ supported }}
+#
ACCESS-ESM
@@ -7,7 +7,7 @@ ACCESS-ESM stands for ACCESS **E**arth **S**ystem **M**odel. Earth system model
ACCESS-NRI will release an ACCESS-ESM model configuration. The first release of ACCESS-ESM will be derived from the [CSIRO ACCESS-ESM1.5 configuration](#access-esm15) and will include [atmosphere], [land] and [land biogeochemistry], [ocean] and [ocean biogeochemistry], and [sea ice] components.
-##
[ACCESS-ESM1.5] {{ recommended }}
+##
[ACCESS-ESM1.5]
[**Citation** [@Ziehn2020-fq]][ACCESS-ESM1.5-cite]
diff --git a/docs/models/configurations/access-om.md b/docs/models/configurations/access-om.md
index 0f4f29ea7..38b0ded94 100644
--- a/docs/models/configurations/access-om.md
+++ b/docs/models/configurations/access-om.md
@@ -1,18 +1,19 @@
-#
ACCESS-OM {{ supported }}
+#
ACCESS-OM
-ACCESS-OM stands for ACCESS **O**cean **M**odel. There is more than just an ocean model, but it indicates that this is not a fully-coupled model, i.e. not coupled with a model atmosphere, the atmospheric fields that drive the model are provided by a data product, usually derived from reanalysis.
+The ACCESS **O**cean **M**odel, ACCESS-OM, is a global coupled ocean and sea ice configuration. It couples the ocean and sea ice components via a coupler. The atmospheric fields that drive the model are provided by a data product, usually derived from reanalysis.
-ACCESS-NRI will release an ACCESS-OM model configuration. The first release of ACCESS-OM will be derived from the COSIMA ACCESS-OM2 suite and will include [ocean] and [sea ice] components.
+ACCESS-NRI will release supported ACCESS-OM configurations. The first release will be derived from the COSIMA [ACCESS-OM2][COSIMA-models] suite and will include [ocean] and [sea ice] components.
-##
[ACCESS-OM2][COSIMA-models] {{ recommended }}
+
+##
[ACCESS-OM2][COSIMA-models]
[**Citation** [@Kiss2020-gmd]][ACCESS-OM2-cite] |
[**Documentation**][ACCESS-OM2-docs]
-ACCESS-OM2 [@Kiss2020-gmd] is a suite of coupled ocean-sea ice models developed by the [Consortium for Ocean-Sea Ice Modelling in Australia (COSIMA)][COSIMA]. All models use the [MOM5] ocean model coupled to the [CICE5] sea ice model via OASIS3-MCT.
+ACCESS-OM2 [@Kiss2020-gmd] is a suite of coupled ocean-sea ice models developed by the Consortium for Ocean-Sea Ice Modelling in Australia ([COSIMA][COSIMA]). All models use the [MOM5] ocean model coupled to the [CICE5] sea ice model via an OASIS3-MCT coupler.
The models in the ACCESS-OM2 suite differ by their grid spatial resolution:
diff --git a/docs/models/configurations/access-s.md b/docs/models/configurations/access-s.md
index ff31c0733..c4590e53c 100644
--- a/docs/models/configurations/access-s.md
+++ b/docs/models/configurations/access-s.md
@@ -1,4 +1,4 @@
-#
[ACCESS-S][ACCESS-S] {{ community }}
+#
[ACCESS-S][ACCESS-S]
diff --git a/docs/models/model_components/aerosols_atmospheric_chemistry.md b/docs/models/model_components/aerosols_atmospheric_chemistry.md
index d7066130f..8479d6b8e 100644
--- a/docs/models/model_components/aerosols_atmospheric_chemistry.md
+++ b/docs/models/model_components/aerosols_atmospheric_chemistry.md
@@ -6,7 +6,7 @@
-##
[UKCA][ukca-wiki] {{ supported }}
+##
[UKCA][ukca-wiki]
The [UK Chemistry-Aerosol model (UKCA)][ukca-wiki] is a community atmospheric chemistry-aerosol global model developed in the United Kingdom. It is suitable for a range of topics in climate and environmental change research.
@@ -16,7 +16,7 @@ UKCA chemistry model is enabled in ACCESS-CM2-Chem.
-##
[GLOMAP][glomap-wiki] {{ supported }}
+##
[GLOMAP][glomap-wiki]
UKCA contains an aerosol scheme [GLObal Model of Aerosol Processes (GLOMAP)][glomap-wiki] that can be used independently. The multi-component, multi-modal GLOMAP model allows simulation of aerosol number, size and concentrations of individual components such as sulphate,sea salt and different types of carbon.
diff --git a/docs/models/model_components/atmosphere.md b/docs/models/model_components/atmosphere.md
index 0cdb3bd87..3ccb7c25d 100644
--- a/docs/models/model_components/atmosphere.md
+++ b/docs/models/model_components/atmosphere.md
@@ -6,7 +6,7 @@
-##
The Unified Model (UM) {{ supported }}
+##
The Unified Model (UM)
[The Unified Model (UM)][um-web] is a numerical model of the atmosphere used for both weather and climate applications, developed by the [Met Office][metoffice-web] in the United Kingdom (UK). It includes solutions of the equations of atmospheric fluid dynamics with advanced parameterizations of subgrid-scale physical processes like convection, cloud formation and atmospheric radiation.
diff --git a/docs/models/model_components/bgc_land.md b/docs/models/model_components/bgc_land.md
index 3b0b96130..86ee66a21 100644
--- a/docs/models/model_components/bgc_land.md
+++ b/docs/models/model_components/bgc_land.md
@@ -7,14 +7,14 @@
-##
[CASA-CNP][casa-web] {{ supported }}
+##
[CASA-CNP][casa-web]
-CASA (Carnegie-Ames-Stanford Approach)-CNP (Carbon-Nitrogen-Phosphorous) is the land biogeochemistry model developed in CABLE.
-
-CASA-CNP models the dynamics of carbon pools and nitrogen and phosphorous limitations. It is directly coupled with the CABLE land surface model.
+[CASA-CNP][casa-web], the Carnegie-Ames-Stanford Approach with Carbon-Nitrogen-Phosphorus, is the biogeochemical module implemented in the ACCESS land surface model [CABLE][cable-wiki]. It models the dynamics of carbon pools and the dependance of carbon uptake due to nitrogen and phosphorous limitations.
+
### How is CASA-CNP used?
-CASA-CNP is switched on for carbon-cycle to use in the ACCESS-ESM1.5 model.
+In the ACCESS-ESM1.5 model, CASA-CNP is enabled within CABLE for the simulation of the carbon cycle.
-[casa-web]: https://carbonwaterobservatory.csiro.au/casa.html
\ No newline at end of file
+[casa-web]: https://carbonwaterobservatory.csiro.au/casa.html
+[cable-wiki]: https://trac.nci.org.au/trac/cable/wiki
\ No newline at end of file
diff --git a/docs/models/model_components/bgc_ocean.md b/docs/models/model_components/bgc_ocean.md
index b5277feb9..638902b65 100644
--- a/docs/models/model_components/bgc_ocean.md
+++ b/docs/models/model_components/bgc_ocean.md
@@ -6,7 +6,7 @@
-##
WOMBAT {{ supported }}
+##
WOMBAT
WOMBAT is the ocean carbon model (World Ocean Model of Biogeochemistry And Trophic-dynamics), developed in Australia. It calculates the carbon fluxes of the ocean, by simulating the evolution of phosphate, oxygen, dissolved inorganic carbon, alkalinity and iron with one class of phytoplankton and zooplankton.
WOMBAT is a Nutrient, Phytoplankton, Zooplankton and Detritus (NPZD) model, with one zooplankton and one phytoplankton class.
diff --git a/docs/models/model_components/coupler.md b/docs/models/model_components/coupler.md
index fa0ce2f9a..f36a6d52d 100644
--- a/docs/models/model_components/coupler.md
+++ b/docs/models/model_components/coupler.md
@@ -1,23 +1,26 @@
-#
Coupler {{ supported }}
+#
Coupler
-A coupler is a software used to perform simulations with different model components at the same time. The coupler enables the different model components to exchange information during the simulation.
+A coupler is a software package that allows synchronised exchanges of coupling information between numerical codes representing different components of the climate system.
-##
[OASIS3-MCT][OASIS3-MCT] {{ supported }}
+##
[OASIS3-MCT][OASIS3-MCT]
-OASIS3-MCT consists of the OASIS coupler interfaced with the Model Coupling Toolkit (MCT) from the Argonne National Laboratory. OASIS3-MCT is the coupler used for:
+[OASIS3-MCT][OASIS3-MCT] is the version of the Ocean Atmosphere Sea Ice Soil (OASIS) coupler interfaced with the Model Coupling Toolkit (MCT) from the Argonne National Laboratory. OASIS3-MCT is the coupler used in the configurations:
- ACCESS-ESM1.5
-- ACCESS-CM2
+- ACCESS-CM2
- ACCESS-OM2
-- ACCESS-S1
+- ACCESS-S
-##
[NUOPC interoperability layer][NUOPC] {{ recommended }}
+##
[NUOPC interoperability layer][NUOPC]
-The NUOPC interoperability layer is distributed via the Earth System Modelling Framework (ESMF). It is a coupler developed by the National Unified Operational Prediction Capability (NUOPC), a consortium of Navy (USA), NOAA and Air Force (USA) modelers.
+[NUOPC][NUOPC-int-layer] (National Unified Operational Prediction Capability) Interoperability Layer defines conventions and a set of generic components for building coupled models using the Earth System Modeling Framework (ESMF).
+
+ACCESS-OM3, a configuration currently under development, uses [NUOPC to couple its MOM6 and CICE6 model components][coupler-choice] as there are no respective OASIS coupling interfaces for these components.
[OASIS3-MCT]: https://oasis.cerfacs.fr/en/
-[NUOPC]: https://earthsystemmodeling.org/nuopc/
\ No newline at end of file
+[NUOPC-int-layer]: https://earthsystemmodeling.org/nuopc/
+[coupler-choice]: https://github.com/COSIMA/access-om3/discussions/7
\ No newline at end of file
diff --git a/docs/models/model_components/land.md b/docs/models/model_components/land.md
index d6937599c..9406427c7 100644
--- a/docs/models/model_components/land.md
+++ b/docs/models/model_components/land.md
@@ -6,7 +6,7 @@
-##
[CABLE][cable-wiki] {{ supported }}
+##
[CABLE][cable-wiki]
[Community Atmosphere Biosphere Land Exchange (CABLE)][cable-web] is a land surface model, used to calculate the fluxes of momentum, energy, water and carbon between the land surface and the atmosphere. It also models the main biogeochemical cycles of the land ecosystem when used in conjunction with [the CASA-CNP module][casa-cnp].
@@ -20,7 +20,7 @@ CABLE is an open source model developed by a community of Australian climate sci
[um-web]: https://www.metoffice.gov.uk/research/approach/modelling-systems/unified-model
-##
[JULES][jules-web] {{ supported }}
+##
[JULES][jules-web]
The [Joint UK Land Environment System (JULES)](jules-web) is a community land surface model that can be used both as a standalone model and as the land surface component in the UM model. By modelling different land surface processes (surface energy balance, hydrological cycle, carbon cycle, dynamic vegetation, etc.) and their interaction with each other, JULES provides a framework to assess the impact of modifying a particular process on the ecosystem as a whole, e.g., the impact of climate change on hydrology.
diff --git a/docs/models/model_components/ocean.md b/docs/models/model_components/ocean.md
index 17e48258e..76ff1a95b 100644
--- a/docs/models/model_components/ocean.md
+++ b/docs/models/model_components/ocean.md
@@ -6,17 +6,16 @@
-##
[Modular Ocean Model (MOM)][mom-wiki] {{ supported }}
+##
[Modular Ocean Model (MOM)][mom-wiki]
The [Modular Ocean Model (MOM)][mom-wiki] is one of the ocean components of the ACCESS climate model system. Used to simulate ocean currents at both regional and global scales, MOM is an invaluable tool for studying the global ocean climate system, as well as capabilities for regional and coastal applications.
-test sentence
+###
MOM5
-###
[MOM5][mom5-github] {{ supported }}
[**Source Code**][mom5-github]
MOM5 is used in supported configurations, such as ACCESS-OM2, ACCESS-CM2 and ACCESS-ESM1.5.
-###
[MOM6][gfdl-web] {{ recommended }}
+###
MOM6
[**Source Code**][mom6-github] |
[**Tutorials**][mom6-tutes]
diff --git a/docs/models/model_components/sea-ice.md b/docs/models/model_components/sea-ice.md
index f68373569..c7f39993e 100644
--- a/docs/models/model_components/sea-ice.md
+++ b/docs/models/model_components/sea-ice.md
@@ -6,7 +6,7 @@
-##
CICE {{ supported }}
+##
CICE
CICE is a numerical model for simulating the growth, melting and movement of polar sea ice. This software package was developed by researchers at [Los Alamos National Laboratory team][lanl-web] and is currently managed by the [CICE Consortium][cice-web], an international group of institutions formed to maintain and develop CICE in the public domain.
[CICE5][cice5-wiki] is the current version used in ACCESS model configurations.
diff --git a/docs/models/running-a-model/getting_started/access_to_gadi_at_nci.md b/docs/models/run-a-model/getting_started/access_to_gadi_at_nci.md
similarity index 100%
rename from docs/models/running-a-model/getting_started/access_to_gadi_at_nci.md
rename to docs/models/run-a-model/getting_started/access_to_gadi_at_nci.md
diff --git a/docs/models/running-a-model/getting_started/index.md b/docs/models/run-a-model/getting_started/index.md
similarity index 58%
rename from docs/models/running-a-model/getting_started/index.md
rename to docs/models/run-a-model/getting_started/index.md
index 0ad038147..3dfd72dd1 100644
--- a/docs/models/running-a-model/getting_started/index.md
+++ b/docs/models/run-a-model/getting_started/index.md
@@ -5,7 +5,7 @@ If *Model*, *Model Component* or *Model Configuration* are not familiar terms fo
If you have not run a model before, our [Getting Started Guide](./access_to_gadi_at_nci.md) will give you the basics to access the Model infrastructure on the high-performance-computing facility Gadi@NCI.
Detailed guides for the different Model configurations can then be found on the following pages:
-- [Run ACCESS-ESM](../running-access-esm.md) for the ACCESS Earth System Model configurations
-- [Run ACCESS-CM](../running-access-cm.md) for the ACCESS Coupled Model configurations
-- [Run ACCESS-AM](../running-access-am.md) for the ACCESS Atmosphere Model configurations
-- [Run ACCESS-OM](../running-access-om.md) for the ACCESS Ocean Model configurations
\ No newline at end of file
+- [Run ACCESS-ESM](../run-access-esm.md) for the ACCESS Earth System Model configurations
+- [Run ACCESS-CM](../run-access-cm.md) for the ACCESS Coupled Model configurations
+- [Run ACCESS-AM](../run-access-am.md) for the ACCESS Atmosphere Model configurations
+- [Run ACCESS-OM](../run-access-om.md) for the ACCESS Ocean Model configurations
\ No newline at end of file
diff --git a/docs/models/running-a-model/index.md b/docs/models/run-a-model/index.md
similarity index 60%
rename from docs/models/running-a-model/index.md
rename to docs/models/run-a-model/index.md
index d81c020c2..1a1345b2e 100644
--- a/docs/models/running-a-model/index.md
+++ b/docs/models/run-a-model/index.md
@@ -7,7 +7,7 @@ If *Model*, *Model Component* or *Model Configuration* are not familiar terms fo
If you have not run a model before, our [Getting Started Guide](./getting_started/access_to_gadi_at_nci.md) will give you the basics to access the Model infrastructure on the high-performance-computing facility Gadi@NCI.
Detailed guides for the different Model configurations can then be found on the following pages:
-- [Run ACCESS-ESM](./running-access-esm.md) for the ACCESS Earth System Model configurations
-- [Run ACCESS-CM](./running-access-cm.md) for the ACCESS Coupled Model configurations
-- [Run ACCESS-AM](./running-access-am.md) for the ACCESS Atmosphere Model configurations
-- [Run ACCESS-OM](./running-access-om.md) for the ACCESS Ocean Model configurations
\ No newline at end of file
+- [Run ACCESS-ESM](./run-access-esm.md) for the ACCESS Earth System Model configurations
+- [Run ACCESS-CM](./run-access-cm.md) for the ACCESS Coupled Model configurations
+- [Run ACCESS-AM](./run-access-am.md) for the ACCESS Atmosphere Model configurations
+- [Run ACCESS-OM](./run-access-om.md) for the ACCESS Ocean Model configurations
\ No newline at end of file
diff --git a/docs/models/running-a-model/running-access-am.md b/docs/models/run-a-model/run-access-am.md
similarity index 100%
rename from docs/models/running-a-model/running-access-am.md
rename to docs/models/run-a-model/run-access-am.md
diff --git a/docs/models/running-a-model/running-access-cm.md b/docs/models/run-a-model/run-access-cm.md
similarity index 97%
rename from docs/models/running-a-model/running-access-cm.md
rename to docs/models/run-a-model/run-access-cm.md
index f4e9ebdce..ad8cfb96d 100644
--- a/docs/models/running-a-model/running-access-cm.md
+++ b/docs/models/run-a-model/run-access-cm.md
@@ -10,7 +10,7 @@ It is also built as a future point of reference, where you can come back and fin
- A Linux/Mac/Unix computer with an internet connection and a command line terminal (e.g., MacOS with XQuartz and command line tools installed, or Putty Cygwin/MobaXterm/similar X-Windows compatible program on a PC).
### Requirements for running ACCESS-CM suites
-Here, we assume that you already have access to Gadi, the supercomputer hosted by the National Computational Infrastructure (NCI). If needed, you can go back to our guide on how to get [access to Gadi](../running-a-model/getting_started/access_to_gadi_at_nci.md).
+Here, we assume that you already have access to Gadi, the supercomputer hosted by the National Computational Infrastructure (NCI). If needed, you can go back to our guide on how to get [access to Gadi](../run-a-model/getting_started/access_to_gadi_at_nci.md).
#### Basic Setup
To run an ACCESS-CM suite, new users will need to:
@@ -51,7 +51,7 @@ Aliases and shortcuts can be created to simplify these commands by [configuring
# Copy, Edit, and Run an ACCESS-CM2 suite
-ACCESS-CM2 is a set of sub-models (eg. UM, MOM, CICE, CABLE, OASIS) with a range of model parameters, input data, and computer related information, that need to be packaged together as a
suite in order to run.
+ACCESS-CM2 is a set of submodels (eg. UM, MOM, CICE, CABLE, OASIS) with a range of model parameters, input data, and computer related information, that need to be packaged together as a
suite in order to run.
Each ACCESS-CM2 suite has an ID, in the format
u-<suite-name>
, with
<suite-name>
being a unique identifier (e.g.
u-br565
is the CMIP6 release preindustrial experiment suite).
@@ -184,11 +184,11 @@ After completing all the modifications to the suite, we are ready to run it.
ACCESS-CM2 suites run on
Gadi through a PBS job submission.
-When the suite gets run, the suite configuration files are copied on Gadi under
/scratch/<$PROJECT>/$USER/cylc-run/<suite-ID>
, and a symbolic link to this folder is also created in the
$USER
's home directory under
~/cylc-run/<suite-ID>
.
+When the suite gets run, its configuration files are copied on Gadi under
/scratch/$PROJECT/$USER/cylc-run/<suite-ID>
, and a symbolic link to this folder is also created in the
$USER
's home directory under
~/cylc-run/<suite-ID>
.
An ACCESS-CM2 suite is constituted by several tasks (such as checking out code repositories, compiling and building the different model components, running the model, etc.). The workflow of these tasks is controlled by Cylc.
-
Cylc (pronounced ‘silk’), is a workflow manager that automatically executes tasks according to the model main cycle script
suite.rc
. Cylc deals with how the job will be run and manages the time steps of each sub-model, as well as monitoring all the tasks and reporting any error that might occur.
+
Cylc (pronounced ‘silk’), is a workflow manager that automatically executes tasks according to the model main cycle script
suite.rc
. Cylc deals with how the job will be run and manages the time steps of each submodel, as well as monitoring all the tasks and reporting any error that might occur.
To run an ACCESS-CM2 suite, on
accessdev:
@@ -481,7 +481,7 @@ This directory contains 2 subdirectories:
References
-
+
-
https://confluence.csiro.au/display/ACCESS/Using+CM2+suites+in+Rose+and+Cylc
diff --git a/docs/models/run-a-model/run-access-esm.md b/docs/models/run-a-model/run-access-esm.md
new file mode 100644
index 000000000..d012ce066
--- /dev/null
+++ b/docs/models/run-a-model/run-access-esm.md
@@ -0,0 +1,416 @@
+
+# Run ACCESS-ESM
+
+
+## Requirements
+
+Before running ACCESS-ESM, you need to make sure to possess the right tools and to have an account with specific institutions.
+
+
+### General requirements
+
+
+### Model-specific requirements
+
+----------------------------------------------------------------------------------------
+
+## Get ACCESS-ESM configuration
+
+A suitable ACCESS-ESM pre-industrial configuration is avaible on the
coecms GitHub.
+
+In order to get it, on Gadi, create a directory where to keep the model configuration, and clone the GitHub repo in it by running:
+
git clone https://github.com/coecms/esm-pre-industrial
+
+ mkdir -p ~/access-esm
+ cd ~/access-esm
+ git clone https://github.com/coecms/esm-pre-industrial
+ Cloning into 'esm-pre-industrial'...
+ remote: Enumerating objects: 767, done.
+ remote: Counting objects: 100% (295/295), done.
+ remote: Compressing objects: 100% (138/138), done.
+ remote: Total 767 (delta 173), reused 274 (delta 157), pack-reused 472
+ Receiving objects: 100% (767/767), 461.57 KiB | 5.24 MiB/s, done.
+ Resolving deltas: 100% (450/450), done.
+
+
Note: Some modules might interfere with the
git
commands (for example matlab/R2018a). If you are running into issues during the cloning of the repository, it might be a good idea to run
module purge
first, before trying again.
+
+----------------------------------------------------------------------------------------
+
+## Edit ACCESS-ESM configuration
+
+In order to modify an ACCESS-ESM configuration, it is worth understanding a bit more how its job scheduler payu works.
+
+
+### Payu
+
+
Payu is a workflow management tool for running numerical models in supercomputing environments.
+
+The general layout of a
payu-supported model run consists of two main directories:
+
+ -
+ The laboratory is the directory where all parts of the model are kept. For ACCESS-ESM, it is typically
/scratch/$PROJECT/$USER/access-esm
.
+
+ -
+ The control directory, where the model configuration is kept and from where the model is run (in our case is the cloned directory
~/access-esm/esm-pre-industrial
).
+
+
+This distinction of directories keeps the small-size configuration files separated from the larger binary outputs and inputs. In this way, we can place the configuration files in the
$HOME
directory (being the only filesystem on Gadi that is actively backed up), without overloading it with too much data.
+
+Moreover, this separation allows to run multiple self-resubmitting experiments simultaneously that might share common executables and input data.
+
+To proceed with the setup of the
laboratory directory, from the
control directory run:
+
payu init
+This will create the
laboratory directory, along with other subdirectories (depending on the configuration). The main subdirectories we are interested in are:
+
+ work
→ temporary directory where the model is actually run. It gets cleaned after each run.
+ archive
→ directory where the output is placed after each run.
+
+ cd ~/access-esm/esm-pre-industrial
+ payu init
+ laboratory path: /scratch/$PROJECT/$USER/access-esm
+ binary path: /scratch/$PROJECT/$USER/access-esm/bin
+ input path: /scratch/$PROJECT/$USER/access-esm/input
+ work path: /scratch/$PROJECT/$USER/access-esm/work
+ archive path: /scratch/$PROJECT/$USER/access-esm/archive
+
+
+
+
+### Edit the Master Configuration file
+
+The
config.yaml
file, located in the
control directory, is the Master Configuration file.
+
+This file controls the general model configuration and if we open it in a text editor, we can see different parts:
+
+ -
+ PBS resources
+
+ jobname: pre-industrial
+ queue: normal
+ walltime: 20:00:00
+
+ These are settings for the PBS scheduler. Edit lines in this section to change any of the PBS resources.
+
+ For example, to run ACCESS-ESM under the tm70
project (TO DO add Getting started, join a NCI Project link), add the following line to this section:
+ project: tm70
+
+ -
+ Link to the laboratory directory
+
+ # note: if laboratory is relative path, it is relative to /scratch/$PROJECT/$USER
+ laboratory: access-esm
+
+ This will set the laboratory directory. Relative paths are relative to /scratch/$PROJECT/$USER
. Absolute paths can be specified as well.
+
+ -
+ Model
+
model: access
+ The main model. This tells payu which driver to use (access stands for ACCESS-ESM).
+
+ -
+ Submodels
+
+ submodels:
+ - name: atmosphere
+ model: um
+ ncpus: 192
+ exe: /g/data/access/payu/access-esm/bin/coe/um7.3x
+ input:
+ - /g/data/access/payu/access-esm/input/pre-industrial/atmosphere
+ - /g/data/access/payu/access-esm/input/pre-industrial/start_dump
+ - name: ocean
+ model: mom
+ ncpus: 180
+ exe: /g/data/access/payu/access-esm/bin/coe/mom5xx
+ input:
+ - /g/data/access/payu/access-esm/input/pre-industrial/ocean/common
+ - /g/data/access/payu/access-esm/input/pre-industrial/ocean/pre-industrial
+ - name: ice
+ model: cice
+ ncpus: 12
+ exe: /g/data/access/payu/access-esm/bin/coe/cicexx
+ input:
+ - /g/data/access/payu/access-esm/input/pre-industrial/ice
+ - name: coupler
+ model: oasis
+ ncpus: 0
+ input:
+ - /g/data/access/payu/access-esm/input/pre-industrial/coupler
+
+ ACCESS-ESM is a coupled model, which means it has multiple submodels (i.e. model components).
+
+ This section specifies the submodels and contains configuration options (for example the directories of input files) that are required to ensure the model can execute correctly. Each submodel also has additional configuration options that are read in when the submodel is running. These specific configuration options are found in the subdirectory of the control directory having the name of the submodel (e.g. in our case the configuration for the atmosphere submodel, i.e. the UM, will be in the directory ~/access-esm/esm-pre-industrial/atmosphere
).
+
+ -
+ collate
+
+ collate:
+ exe: /g/data/access/payu/access-esm/bin/mppnccombine
+ restart: true
+ mem: 4GB
+
+ The collate process joins a number of smaller files, which contain different parts of the model grid, together into target output files. The restart files are typically tiled in the same way and will also be joined together if the restart option is set to true
.
+
+ -
+ restart
+
+ restart: /g/data/access/payu/access-esm/restart/pre-industrial
+ The location of the files used for a warm restart.
+
+ -
+ Start date and internal run length
+
+ calendar:
+ start:
+ year: 101
+ month: 1
+ days: 1
+ runtime:
+ years: 1
+ months: 0
+ days: 0
+
+ This section specifies the start date and internal run length.
+
+ Note: The internal run length (controlled by runtime
) can be different from the total run length. Also, the runtime
value can be lowered, but should not be increased to a total of more than 1 year, to avoid errors. If you want to know more about the difference between internal run and total run lenghts, or if you want to run the model for more than 1 year, check Run configuration for multiple years.
+
+ -
+ Number of runs per PBS submission
+
+ runspersub: 5
+ ACCESS-ESM configurations are often run in multiple steps (or cycles), with payu running a maximum of runspersub
internal runs for every PBS job submission.
+
+ Note: If we increase runspersub
, we might need to increase the walltime in the PBS resources.
+
+
+To know more about other configuration settings for the
config.yaml
file, please check
how to configure your experiment with payu.
+
+----------------------------------------------------------------------------------------
+
+## Run ACCESS-ESM configuration
+After editing the configuration, we are ready to run ACCESS-ESM.
+
+ACCESS-ESM suites run on Gadi through a PBS job submission managed by payu.
+
+### Payu setup (optional)
+
+As a first step, from the control directory, is good practice to run:
+
payu setup
+This will prepare the model run, based on the experiment configuration.
+
+ payu setup
+ laboratory path: /scratch/$PROJECT/$USER/access-esm
+ binary path: /scratch/$PROJECT/$USER/access-esm/bin
+ input path: /scratch/$PROJECT/$USER/access-esm/input
+ work path: /scratch/$PROJECT/$USER/access-esm/work
+ archive path: /scratch/$PROJECT/$USER/access-esm/archive
+ Loading input manifest: manifests/input.yaml
+ Loading restart manifest: manifests/restart.yaml
+ Loading exe manifest: manifests/exe.yaml
+ Setting up atmosphere
+ Setting up ocean
+ Setting up ice
+ Setting up coupler
+ Checking exe and input manifests
+ Updating full hashes for 3 files in manifests/exe.yaml
+ Creating restart manifest
+ Updating full hashes for 30 files in manifests/restart.yaml
+ Writing manifests/restart.yaml
+ Writing manifests/exe.yaml
+
+
Note: You can skip this step as it is included also in the run command. However, runnning it explicitly helps to check for errors and make sure executable and restart directories are accessible.
+
+
+### Run configuration
+
+To run ACCESS-ESM configuration for one internal run length (controlled by
runtime
in the
config.yaml
file), run:
+
payu run -f
+This will submit a single job to the queue with a total run length of
runtime
. It there is no previous run, it will start from the
start
date indicated in the
config.yaml
file, otherwise it will perform a warm restart from a precedently saved restart file.
+
+
Note:The
-f
option ensures that
payu will run even if there is an existing non-empty
work directory, which happens if a run crashes.
+
+ payu run -f
+ Loading input manifest: manifests/input.yaml
+ Loading restart manifest: manifests/restart.yaml
+ Loading exe manifest: manifests/exe.yaml
+ payu: Found modules in /opt/Modules/v4.3.0
+ qsub -q normal -P <project> -l walltime=11400 -l ncpus=384 -l mem=1536GB -N pre-industrial -l wd -j n -v PAYU_PATH=/g/data/hh5/public/apps/miniconda3/envs/analysis3-23.01/bin,MODULESHOME=/opt/Modules/v4.3.0,MODULES_CMD=/opt/Modules/v4.3.0/libexec/modulecmd.tcl,MODULEPATH=/g/data3/hh5/public/modules:/etc/scl/modulefiles:/opt/Modules/modulefiles:/opt/Modules/v4.3.0/modulefiles:/apps/Modules/modulefiles -W umask=027 -l storage=gdata/access+gdata/hh5 -- /g/data/hh5/public/apps/miniconda3/envs/analysis3-23.01/bin/python3.9 /g/data/hh5/public/apps/miniconda3/envs/analysis3-23.01/bin/payu-run
+ <job-ID>.gadi-pbs
+
+
+
+### Run configuration for multiple years
+
+If you want to run ACCESS-ESM configuration for multiple internal run lengths (controlled by
runtime
in the
config.yaml
file), you can use the option
-n
:
+
payu run -n <number-of-runs>
+This will run the configuration
number-of-runs
times with a total run length of
runtime * number-of-runs
. The number of consecutive PBS jobs submitted to the queue depends on the
runspersub
value specified in the
config.yaml
file.
+
+
+### Understand runtime
, runspersub
, and -n
parameters
+
+With the correct use of
runtime
,
runspersub
, and
-n
parameters, we can have full control of our run.
+
+
+ -
+
runtime
defines the internal run length.
+
+ -
+
runspersub
defines the maximum number of internal runs for every PBS job submission.
+
+ -
+
-n
sets the number of internal runs to be performed.
+
+
+Let's have some practical examples:
+
+
+----------------------------------------------------------------------------------------
+
+## Monitor runs
+
+Currently, there is no specific tool to monitor ACCESS-ESM runs.
+
+One way to check the status of our run is running:
+
qstat -u $USER
+This will show the status of all your PBS jobs (if there is any PBS job submitted):
+
+ qstat -u $USER
+ Job id Name User Time Use S Queue
+ --------------------- ---------------- ---------------- -------- - -----
+ <job-ID>.gadi-pbs pre-industrial <$USER> <time> R normal-exec
+ <job-ID>.gadi-pbs <other-job-name> <$USER> <time> R normal-exec
+ <job-ID>.gadi-pbs <other-job-name> <$USER> <time> R normal-exec
+
+If you changed the
jobname
in the PBS resources of the
Master Configuration file, that will be your job's
Name instead of
pre-industrial
.
+
+
S indicates the status of your run:
+
+ - Q → Job waiting in the queue to start
+ - R → Job running
+ - E → Job ending
+
+If there is no listed job with your
jobname
(or if there is no job submitted at all), your run might have successfully completed, or might have been terminated due to an error.
+
+
+### Check the output and error log files
+
+While the model is running, payu saves the standard output and standard error into the files access.out
and access.err
in the control directory. You can examine these files, as the run progresses, to check on it's status.
+
+After the model has completed its run, or if it crashed, the output and error log files, respectively, are renamed by default into jobname.o<job-ID>
and jobname.e<job-ID>
.
+
+----------------------------------------------------------------------------------------
+
+## Model outputs
+
+While the configuration is running, output files (as well as restart files) are moved from the
work
directory to the
archive
directory, under
/scratch/$PROJECT/$USER/access-esm/archive
(also symlinked in the
control directory under
~/access-esm/esm-pre-industrial/archive
).
+
+Both outputs and restarts are stored into subfolders for each different configuration (
esm-pre-industrial
in our case), and inside the configuration folder, they are subdivided for each internal run.
+
+The format of a typical output folder is
outputXXX
, whereas the typical restart folder is usually formatted as
restartXXX
, with
XXX being the number of internal run, starting from
000
.
+
+In the respective folders, outputs and restarts are separated for each model component.
+
+For the atmospheric output data, each file it is usually a
UM fieldsfile, formatted as
<UM-suite-identifier>a.p<output-stream-identifier><time-identifier>
.
+
+ cd /scratch/$PROJECT/$USER/access-esm/archive/esm-pre-industrial
+ ls
+ output000 pbs_logs restart000
+ ls output000/atmosphere
+ aiihca.daa1210 aiihca.daa1810 aiihca.paa1apr aiihca.paa1jun aiihca.pea1apr aiihca.pea1jun aiihca.pga1apr aiihca.pga1jun atm.fort6.pe0 exstat ihist prefix.CNTLGEN UAFLDS_A aiihca.daa1310 aiihca.daa1910 aiihca.paa1aug aiihca.paa1mar aiihca.pea1aug aiihca.pea1mar aiihca.pga1aug aiihca.pga1mar cable.nml fort.57 INITHIS prefix.PRESM_A um_env.py aiihca.daa1410 aiihca.daa1a10 aiihca.paa1dec aiihca.paa1may aiihca.pea1dec aiihca.pea1may aiihca.pga1dec aiihca.pga1may CNTLALL ftxx input_atm.nml SIZES xhist aiihca.daa1510 aiihca.daa1b10 aiihca.paa1feb aiihca.paa1nov aiihca.pea1feb aiihca.pea1nov aiihca.pga1feb aiihca.pga1nov CONTCNTL ftxx.new namelists STASHC aiihca.daa1610 aiihca.daa1c10 aiihca.paa1jan aiihca.paa1oct aiihca.pea1jan aiihca.pea1oct aiihca.pga1jan aiihca.pga1oct debug.root.01 ftxx.vars nout.000000 thist aiihca.daa1710 aiihca.daa2110 aiihca.paa1jul aiihca.paa1sep aiihca.pea1jul aiihca.pea1sep aiihca.pga1jul aiihca.pga1sep errflag hnlist prefix.CNTLATM UAFILES_A
+
+
+
+
+
+
+
+References
+
\ No newline at end of file
diff --git a/docs/models/running-a-model/running-access-om.md b/docs/models/run-a-model/run-access-om.md
similarity index 100%
rename from docs/models/running-a-model/running-access-om.md
rename to docs/models/run-a-model/run-access-om.md
diff --git a/docs/models/running-a-model/running-access-esm.md b/docs/models/running-a-model/running-access-esm.md
deleted file mode 100644
index e69de29bb..000000000
diff --git a/docs/models/running-a-model/running-access-s.md b/docs/models/running-a-model/running-access-s.md
deleted file mode 100644
index e69de29bb..000000000
diff --git a/mkdocs.yml b/mkdocs.yml
index ed8bcc7b4..0c4440686 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -15,11 +15,17 @@ theme:
name: material
custom_dir: overrides
palette:
- - scheme: custom-light
+
+ # Palette toggle for light mode
+ - media: "(prefers-color-scheme: light)"
+ scheme: custom-light
toggle:
icon: material/theme-light-dark
name: Switch to dark mode
- - scheme: custom-dark
+
+ # Palette toggle for dark mode
+ - media: "(prefers-color-scheme: dark)"
+ scheme: custom-dark
toggle:
icon: material/theme-light-dark
name: Switch to light mode
@@ -41,11 +47,6 @@ theme:
- search.share
- toc.follow # the sidebar is automatically scrolled to the active anchor
- # - navigation.expand
- # - navigation.path
- # - toc.integrate
- # - navigation.sections
-
logo: assets/ACCESS_icon_HIVE.png
favicon: assets/ACCESS_icon_HIVE.png
icon:
@@ -75,17 +76,21 @@ markdown_extensions:
- pymdownx.details
- pymdownx.superfences
- pymdownx.inlinehilite
+ - pymdownx.tabbed:
+ alternate_style: true
- def_list
- footnotes
- tables
- pymdownx.keys
+ - toc:
+ title: On this page
# Navigation
nav:
- Home:
- index.md
- Contact: about/contact.md
- - Support: about/support.md
+ - User support: about/user_support.md
- Contribute:
- Contribute: contribute/index.md
- Edit on Github: contribute/edit-on-github.md
@@ -118,16 +123,16 @@ nav:
- ACCESS-OM: models/configurations/access-om.md
- Run a Model:
- - models/running-a-model/index.md
+ - models/run-a-model/index.md
# If we add an additional subsection
# - Getting Started:
# - models/running-a-model/getting_started/index.md
# - Access to Gadi@NCI: models/running-a-model/getting_started/access_to_gadi_at_nci.md
- - Computing Access (Gadi@NCI): models/running-a-model/getting_started/access_to_gadi_at_nci.md
- - Run ACCESS-ESM: models/running-a-model/running-access-esm.md
- - Run ACCESS-CM: models/running-a-model/running-access-cm.md
- - Run ACCESS-AM: models/running-a-model/running-access-am.md
- - Run ACCESS-OM: models/running-a-model/running-access-om.md
+ - Computing Access (Gadi@NCI): models/run-a-model/getting_started/access_to_gadi_at_nci.md
+ - Run ACCESS-ESM: models/run-a-model/run-access-esm.md
+ - Run ACCESS-CM: models/run-a-model/run-access-cm.md
+ - Run ACCESS-AM: models/run-a-model/run-access-am.md
+ - Run ACCESS-OM: models/run-a-model/run-access-om.md
- Model Evaluation:
- model_evaluation/index.md
@@ -180,8 +185,6 @@ nav:
# Footer
extra:
generator: true
- # version:
- # provider: mike
social:
- icon: fontawesome/brands/twitter
link: https://twitter.com/ACCESS_NRI
@@ -196,28 +199,12 @@ extra:
provider: google
property: G-2T6SQEH2CX
- # Original implementation
- # supported: ''
- # recommended: ''
- # community: ''
-
- # Octicons experimental
- # supported: ':octicons-check-circle-24:{ .icon-supported title="Supported by ACCESS-NRI" }'
- # recommended: ':octicons-star-24:{ .icon-recommended title="Recommended by ACCESS-NRI" }'
- # community: ':octicons-heart-fill-24:{ .heart title="Community contributed" }'
-
- # Material icons experimental
- # supported: 'check_circle_outlined'
- # recommended: 'star'
- # community: 'favorite'
-
- # Fontawesome icons
- supported: ''
- recommended: ''
- community: ''
+ # # Fontawesome icons
+ # supported: ''
+ # recommended: ''
+ # community: ''
extra_css:
- - css/termynal.css
- css/fontello.css
- "https://fonts.googleapis.com/icon?family=Material+Icons" # Material Icons Reference - https://material.io/resources/icons/?style=baseline
- css/fontawesome-free-6.4.0-web/css/fontawesome.css
@@ -226,5 +213,5 @@ extra_css:
extra_javascript:
- https://unpkg.com/tablesort@5.3.0/dist/tablesort.min.js # For tablesort functionality
- - js/termynal.js
+ - js/terminal_animation.js
- js/miscellaneous.js
diff --git a/overrides/partials/toc.html b/overrides/partials/toc.html
index 524a211d0..45f92e04e 100644
--- a/overrides/partials/toc.html
+++ b/overrides/partials/toc.html
@@ -1,8 +1,7 @@
{#-
This file was automatically generated - do not edit
-#}
-
- {% set title = "On this page" %}
+ {% set title = lang.t("toc") %}
{% if config.mdx_configs.toc and config.mdx_configs.toc.title %}
{% set title = config.mdx_configs.toc.title %}
{% endif %}