Modify an ACCESS model's source code
diff --git a/docs/models/run-a-model/run-access-cm.md b/docs/models/run-a-model/run-access-cm.md
index 5cadabd71..99848b918 100644
--- a/docs/models/run-a-model/run-access-cm.md
+++ b/docs/models/run-a-model/run-access-cm.md
@@ -383,7 +383,7 @@ To access a specific task, click on the arrow next to the task to extend the dro
#### Through the suite directory
The suite's log directories are stored in `~/cylc-run/
` as `log.`, and the latest set of logs are also symlinked in the `~/cylc-run//log` directory.
The logs for the main job can be found in the `~/cylc-run//log/job` directory.
-Logs are separated into simulation cycles according to their starting dates, and then differentiated by task. They are then further separated into "attempts" (consecutive failed/successful tasks), where `NN` is a symlink to the most recent attempt.
+Logs are separated into simulation cycles according to their starting dates, then divided into subdirectories according to the task name. They are then further separated into "attempts" (consecutive failed/successful tasks), where `NN` is a symlink to the most recent attempt.
In the example above, a failure occurred for the _09500101_ simulation cycle (i.e. starting date: 1st January 950) in the _coupled_ task. Hence, the `job.err` and `job.out` files can be found in the `~/cylc-run//log/job/09500101/coupled/NN` directory.
diff --git a/docs/models/run-a-model/run-access-ram.md b/docs/models/run-a-model/run-access-ram.md
new file mode 100644
index 000000000..cfe86ca13
--- /dev/null
+++ b/docs/models/run-a-model/run-access-ram.md
@@ -0,0 +1,720 @@
+{% set model = "ACCESS-RAM3" %}
+{% set ancillary_model = "ACCESS-RAS" %}
+{% set regional_model = "ACCESS-RNS" %}
+{% set ras_id = "u-dg767" %}
+{% set rns_id = "u-dg768" %}
+{% set mosrs_config_ras = "https://code.metoffice.gov.uk/trac/roses-u/browser/d/g/7/6/7/trunk" %}
+{% set mosrs_config_rns = "https://code.metoffice.gov.uk/trac/roses-u/browser/d/g/7/6/8/trunk" %}
+[PBS job]: https://opus.nci.org.au/display/Help/4.+PBS+Jobs
+[model components]: /models/configurations/access-ram/#model-components
+[model configurations]: /models/configurations/access-ram
+[gadi]: https://opus.nci.org.au/display/Help/0.+Welcome+to+Gadi#id-0.WelcometoGadi-Overview
+
+[{: class="icon-before-text white-background"} {{ ancillary_model }} configuration]({{mosrs_config_ras}}){: class="text-card" style=""}
+[{: class="icon-before-text white-background"} {{ regional_model }} configuration]({{mosrs_config_rns}}){: class="text-card"}
+
+# Run ACCESS-RAM3
+
+!!! info
+ {{ model }} is a place-holder name until the final release name is chosen.
+
+## About
+
+{{ model }} is an ACCESS-NRI-supported configuration of the [UK Met Office (UKMO)](https://www.metoffice.gov.uk/) Regional Nesting Suite. Driven by ERA5, the configuration comprises a 2-level nest; the outer level uses GAL9 with a resolution of 10km or 11km (depending on the choice of land-surface initial conditions), and the inner nest that focuses on the region of interest uses RAL3.2 with 2.2 km resolution.
+A description of the model and its components is available in the [ACCESS-RAM3 overview][model configurations].
+
+{{ model }} comprises a [Regional Ancillary Suite (RAS)](#ras) (RAS) `{{ ras_id }}` to generate ancillary files needed to run the [Regional Nesting Suite (RNS)](#rns) `{{ rns_id }}` for the domain of interest.
+
+The instructions below outline how to run {{ model }} using ACCESS-NRI's supported configuration, specifically designed to run on the [National Computating Infrastructure (NCI)](https://nci.org.au/about-us/who-we-are) supercomputer [_Gadi_][gadi].
+
+If you are unsure whether {{ model }} is the right choice for your experiment, take a look at the overview of [ACCESS Models](/models).
+
+All {{model}} configurations are open source, licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/?ref=chooser-v1"){: style="height:1em;margin-left:0.2em;vertical-align:text-top;"}{: style="height:1em;margin-left:0.2em;vertical-align:text-top;"} and available on [ACCESS-NRI GitHub]({{github_configs}}).
+
+{{ model }} release notes are available on the ACCESS-Hive Forum and are updated when new releases are made available.
+
+
+
+
+## Quick Start
+
+The following *Quick Start* guide is aimed at experienced users wanting to run {{ model }}. If you would prefer more detailed instructions, please refer to the *Detailed Guide* below.
+
+### Required setup for running {{ model }}
+
+- **Join relevant NCI projects**
_access_, _hr22_, _ki32_, _ki32\_mosrs_, _rt52_, _zz93_ and _vk83_
+
+- **Start a new [persistent session](https://opus.nci.org.au/display/Help/Persistent+Sessions)**
+ using a *Gadi* login node or an ARE terminal instance:
+ ```
+ persistent-sessions start
+ ```
+
+ This will use your default project. Use option `-p` to assign a different project to the persistent session:
+ ```
+ persistent-sessions start -p
+ ```
+
+- **Assign the persistent session**
+ Run the following command:
+ ```
+ echo ".${USER}..ps.gadi.nci.org.au" > ~/.persistent-sessions/cylc-session
+ ```
+ substituting `` with the name given to your persistent session, and `` with the project assigned to it.
+
+- **Cylc setup**
+ To get the required _Cylc_ setup, run:
+ ```
+ module use /g/data/hr22/modulefiles
+ module load cylc7
+ ```
+
+- **MOSRS authentication**
+ Authenticate using your MOSRS credentials:
+ ```
+ mosrs-auth
+ ```
+
+### Regional Ancillary Suite (RAS)
+1. **Copy the RAS from UKMO**
+ Local-only copy:
+ ```
+ rosie checkout {{ ras_id }}
+ ```
+
+ New copy, both _locally_ and _remotely_:
+ ```
+ rosie copy {{ ras_id }}
+ ```
+
+2. **Run the RAS**
+ From within the RAS directory:
+ ```
+ rose suite-run
+ ```
+
+### Regional Nesting Suite (RNS)
+1. **Copy the RNS from UKMO**
+ Local-only copy:
+ ```
+ rosie checkout {{ rns_id }}
+ ```
+
+ New copy, both _locally_ and _remotely_:
+ ```
+ rosie copy {{ rns_id }}
+ ```
+
+2. **Run the RNS**
+ From within the RNS directory:
+ ```
+ rose suite-run
+ ```
+
+!!! tip
+ You've completed all steps in the Quick Start reference. For more comprehensive instructions keep reading below.
+
+---
+
+## Detailed Guide
+
+### Prerequisites
+
+- **NCI Account**
+ Before running {{ model }}, you need to [Set Up your NCI Account](/getting_started/set_up_nci_account).
+
+- **_MOSRS_ account**
+ The [Met Office Science Repository Service (MOSRS)](https://code.metoffice.gov.uk) is a server run by the UK Met Office (UKMO) to support collaborative development with other partners organisations. MOSRS contains the source code and configurations for some model components in {{ model }} (e.g., the [UM](/models/model_components/atmosphere/#unified-model-um)).
+ To apply for a _MOSRS_ account, please contact your [local institutional sponsor](https://opus.nci.org.au/display/DAE/Prerequisites).
+
+- **Join NCI projects**
+ _access_, _hr22_, _ki32_, _ki32\_mosrs_, _rt52_, _zz93_ and _vk83_.
+
+ To join these projects, request membership on the respective [access](https://my.nci.org.au/mancini/project/access/join), [hr22](https://my.nci.org.au/mancini/project/hr22/join), [ki32](https://my.nci.org.au/mancini/project/ki32/join), [ki32_mosrs](https://my.nci.org.au/mancini/project/ki32_mosrs/join), [rt52](https://my.nci.org.au/mancini/project/rt52/join), [zz93](https://my.nci.org.au/mancini/project/zz93/join) and [vk83](https://my.nci.org.au/mancini/project/vk83/join) NCI project pages.
+
+ !!! tip
+ To request membership for the _ki32_mosrs_ subproject you need to be member of the _ki32_ project first.
+
+ For more information on joining specific NCI projects, refer to [How to connect to a project](https://opus.nci.org.au/display/Help/How+to+connect+to+a+project).
+
+- **Connection to an ARE VDI Desktop (optional)**
+ To run {{ model }}, start an [Australian Research Environment (ARE) VDI Desktop](https://are.nci.org.au/pun/sys/dashboard/batch_connect/sys/desktop_vnc/ncigadi/session_contexts/new) session.
+ If you are not familiar with ARE, check out the [Getting Started on ARE](/getting_started/are) section.
+
+### Set up an ARE VDI Desktop (optional)
+!!! info
+ If you want to skip this step and run {{ model }} from _Gadi_ login node instead, refer directly to the instructions on how to [Set up persistent session](#set-up-persistent-session).
+
+#### Launch ARE VDI Session
+Go to the [ARE VDI](https://are.nci.org.au/pun/sys/dashboard/batch_connect/sys/desktop_vnc/ncigadi/session_contexts/new) page and launch a session with the following entries:
+
+- **Walltime (hours)** → `2`
+ This is the amount of time the ARE VDI session will stay active for.
+ {{ model }} does not run directly on ARE.
+ This means that the ARE VDI session only needs to carry out setup steps as well as starting the run itself. All these tasks can be done within 2 hours.
+
+- **Queue** → `normalbw`
+
+- **Compute Size** → `tiny` (1 CPU)
+ As mentioned above, the ARE VDI session is only needed for setup and startup tasks, which can be easily accomplished with 1 CPU.
+
+- **Project** → a project of which you are a member.
+ The project must have allocated _Service Units (SU)_ to run your simulation. Usually, but not always, this corresponds to your `$PROJECT`.
+ For more information, refer to [Join relevant NCI projects](/getting_started/set_up_nci_account#join-relevant-nci-projects).
+
+- **Storage** → `gdata/access+gdata/hr22+gdata/ki32+gdata/rt52+gdata/zz93+gdata/vk83` (minimum)
+ This is a list of all project data storage, joined by plus (`+`) signs, needed for the {{ model }} simulation. In ARE, storage locations need to be explicitly defined to access data from within a VDI instance.
+ Every {{ model }} simulation can be unique and input data can originate from various sources. Hence, if your simulation requires data stored in project folders other than the ones listed in the minimum storage above, you need to add those projects to the storage path.
+ For example, if your {{ model }} simulation requires data stored in `/g/data/tm70` and `/scratch/w40`, the following should be added to the minimum storage above: `+gdata/tm70+scratch/w40`
+
+Launch the ARE session and, once it starts, click on _Launch VDI Desktop_.
+
+{: class="example-img" loading="lazy"}
+
+#### Open the terminal in the VDI Desktop
+Once the new tab opens, you will see a Desktop with a few folders on the left.
+To open the terminal, click on the black terminal icon at the top of the window. You should now be connected to a _Gadi_ computing node.
+
+{: class="example-img" loading="lazy"}
+
+### Set up persistent session
+To support the use of long-running processes, such as ACCESS model runs, NCI provides a service on _Gadi_ called [persistent sessions](https://opus.nci.org.au/display/Help/Persistent+Sessions).
+
+To run {{ model }}, you need to start a persistent session and set it as the target session for the model run.
+
+#### Start a new persistent session
+To start a new persistent session on _Gadi_, using either a login node or an ARE terminal instance, run the following command:
+```
+persistent-sessions start
+```
+
+This will start a persistent session with the given `name` that runs under your [default project](/getting_started/set_up_nci_account#change-default-project-on-gadi).
+If you want to assign a different project to the persistent session, use the option `-p`:
+```
+persistent-sessions start -p
+```
+
+!!! tip
+ While the project assigned to a persistent session does not have to be the same as the project used to run the {{ model }} configuration, it does need to have allocated _Service Units (SU)_.
+ For more information, check how to [Join relevant NCI projects](/getting_started/set_up_nci_account#join-relevant-nci-projects).
+
+
+ persistent-sessions start <name>
+ session <persistent-session-uuid> running - connect using
+ ssh <name>.<$USER>.<project>.ps.gadi.nci.org.au
+
+
+To list all active persistent sessions run:
+```
+persistent-sessions list
+```
+
+
+ persistent-sessions list
+ UUID PROJECT ADDRESS CPUTIME MEMORY
+ <persistent-session-uuid> <project> 10.9.0.62 00:00:05.213 30.5M
+
+
+
+The label of a newly-created persistent session has the following format:
+`.<$USER>..ps.gadi.nci.org.au`.
+
+#### Specify target persistent session
+
+After starting the persistent session, it is essential to assign it to the {{ model }} run.
+The easiest way to create a file `~/.persistent-sessions/cylc-session` that contains the target of the persistent session.
+You can do it manually, or by running the following command (by substituting `` with the name given to the persistent session, and `` with the project assigned to it):
+
+```
+echo ".${USER}..ps.gadi.nci.org.au" > ~/.persistent-sessions/cylc-session
+```
+
+For example, if the user `abc123` started a persistent session named `cylc` under the project `xy00`, the command will be:
+
+
+ echo "cylc.abc123.xy00.ps.gadi.nci.org.au" > ~/.persistent-sessions/cylc-session
+
+ cat ~/.persistent-sessions/cylc-session
+ cylc.abc123.xy00.ps.gadi.nci.org.au
+
+
+For more information on how to specify the target session, refer to [Specify Target Session with Cylc7 Suites](https://opus.nci.org.au/display/DAE/Run+Cylc7+Suites#RunCylc7Suites-SpecifyTargetSession).
+
+!!! tip
+ You can simultaneously submit multiple {{ model }} runs using the same persistent session without needing to start a new one. Hence, the process of specifying the target persistent session for {{ model }} should only be done once.
+ After specifying the {{ model }} target persistent session the first time, to run {{ model }} you just need to make sure to have an active persistent session named like the specified {{ model }} target persistent session.
+
+#### Terminate a persistent session
+!!! tip
+ Logging out of a *Gadi* login node or an ARE terminal instance will not affect your persistent session.
+
+To stop a persistent session, run:
+```
+persistent-sessions kill
+```
+!!! warning
+ When you terminate a persistent session, any model running on that session will stop. Therefore, you should check whether you have any active model runs before terminating a persistent session.
+
+### Rose/Cylc/MOSRS setup
+
+To run {{ model }}, access to multiple softwares and the Met Office Science Repository Service (MOSRS) is needed.
+
+#### Cylc setup {: id="cylc"}
+
+[_Cylc_](https://cylc.github.io/cylc-doc/7.8.8/html/index.html) (pronounced ‘silk’) is a workflow manager that automatically executes tasks according to the model's main cycle script `suite.rc`. _Cylc_ controls how the job will be run and manages the time steps of each model component. It also monitors all tasks, reporting any errors that may occur.
+
+To get the _Cylc_ setup required to run {{ model }}, execute the following commands:
+```
+module use /g/data/hr22/modulefiles
+module load cylc7
+```
+
+ module use /g/data/hr22/modulefiles
+ module load cylc7
+ Using the cylc session <name>.<$USER>.<project>.ps.gadi.nci.org.au
+
+ Loading cylc7/24.03
+ Loading requirement: mosrs-setup/2.0.1
+
+
+!!! warning
+ It is recommended not to specify any version when loading _Cylc_, as versions earlier than `23.09` do not support the persistent sessions workflow.
+ Also, before loading the _Cylc_ module, make sure to have started a persistent session and assigned it to the {{ model }} workflow. For more information about these steps, refer to [Set up persistent session](#set-up-persistent-session).
+
+#### Rose setup {: id="rose"}
+[Rose](http://metomi.github.io/rose/doc/html/index.html) is a toolkit that can be used to view, edit, or run an ACCESS modelling suite.
+
+By completing the [_Cylc_ setup](#cylc), also _Rose_ will be automatically available. Therefore, there is no additional step required.
+
+#### MOSRS authentication
+To authenticate using your _MOSRS_ credentials, run:
+```
+mosrs-auth
+```
+
+ mosrs-auth
+ INFO: You need to enter your MOSRS credentials here so that GPG can cache your password.
+ Please enter the MOSRS password for <MOSRS-username>:
+ Checking your credentials using Subversion. Please wait.
+ INFO: Successfully accessed Subversion with your credentials.
+ INFO: Checking your credentials using rosie. Please wait.
+ INFO: Successfully accessed rosie with your credentials.
+
+
+### {{ model }} configuration
+{{ model }} is comprised of 2 different suites: a [Regional Ancillary Suite (RAS)](#ras) and a [Regional Nesting Suite (RNS)](#rns).
+
+Each {{ model }} suite has a `suite-ID` in the format `u-`, where `` is a unique identifier.
+Typically, an existing suite is copied and then edited as needed for a particular run.
+
+For more information on {{ model }} configuration, check [{{model}}][model configurations] page.
+
+!!! info
+ Many of the steps that follow are to be repeated almost identically for the RAS and RNS. For this reason, details on these steps will be provided only within the RAS section below, whereas in the following RNS section they will only be linked for reference.
+
+### Regional Ancillary Suite (RAS) {: id="ras"}
+
+The RAS produces a set of input (ancillary) files, which are then used by the RNS.
+
+The `suite-ID` of the RAS is `{{ ras_id }}`.
+
+
+#### Get the RAS configuration
+[Rosie](http://metomi.github.io/rose/doc/html/tutorial/rose/rosie.html) is an [SVN](https://subversion.apache.org) repository wrapper with a set of options specific for ACCESS modelling suites. It is automatically available within the [_Rose_ setup](#rose).
+
+The RAS configuration can be obtained as a copy of the MOSRS one, following 2 approaches:
+
+- [Local-only copy](#local-copy)
+- [Remote and local copy](#remote-copy)
+
+Suites are, by default, created in the user's home directory on _Gadi_ under `~/roses/`.
+This path will be referred to as the *suite directory*.
+{: id="suitedir" }
+
+The suite directory contains multiple subdirectories and files, including:
+
+- `app` → directory containing the configuration files for various tasks within the suite.
+- `meta` → directory containing the GUI metadata.
+- `rose-suite.conf` → main suite configuration file.
+- `rose-suite.info` → suite information file.
+- `suite.rc` → _Cylc_ control script file (Jinja2 language).
+
+##### Local-only copy {: id="local-copy"}
+To create a _local copy_ of the RAS from the UKMO repository, run:
+```
+rosie checkout {{ ras_id }}
+```
+
+ rosie checkout {{ ras_id }}
+ [INFO] create: /home/565/<$USER>/roses
+ [INFO] <suite-ID>: local copy created at /home/565/<$USER>/roses/{{ ras_id }}
+
+This option is mostly used for testing and examining existing suites.
+
+##### Remote and local copy {: id="remote-copy"}
+To create a new copy of the RAS both _locally_ and _remotely_ in the UKMO repository, run:
+```
+rosie copy {{ ras_id }}
+```
+
+ rosie copy {{ ras_id }}
+ Copy "{{ ras_id }}/trunk@<trunk-ID>" to "u-?????"? [y or n (default)] y
+ [INFO] <new-suite-ID>: created at https://code.metoffice.gov.uk/svn/roses-u/<suite-n/a/m/e/>
+ [INFO] <new-suite-ID>: copied items from {{ ras_id }}/trunk@<trunk-ID>
+ [INFO] {{ ras_id }}: local copy created at /home/565/<$USER>/roses/<new-suite-ID>
+
+When a new suite is created in this way, a _unique_ `` is generated within the repository and populated with descriptive information about the suite and its initial configuration.
+
+For additional `rosie` options, run:
+```
+rosie help
+```
+
+#### Run the suite
+{{ model }} suites run on [_Gadi_](https://opus.nci.org.au/display/Help/0.+Welcome+to+Gadi#id-0.WelcometoGadi-Overview) through a [PBS job] submission.
+When a suite runs, its configuration files are copied on _Gadi_ inside `/scratch/$PROJECT/$USER/cylc-run/` and a symbolic link to this directory is also created in the `$USER`'s home directory under `~/cylc-run/`.
+{{ model }} suites comprise 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).
+
+
+
+To run the RAS run the following command from within the [suite directory](#suitedir):
+```
+rose suite-run
+```
+
+After the initial tasks are executed, the _Cylc_ GUI will open. You can now view and control the different tasks in the suite as they are run.
+
+
+You are done!
+
+If you do not get any errors, you can check the suite output files after the run is complete.
+You can now close the _Cylc_ GUI. To open it again, run the following command from within the [suite directory](#suitedir):
+```
+rose suite-gcontrol
+```
+
+#### Monitor the suite runs
+
+It is quite common, especially during the first few runs, to experience errors and job failures. Running a suite involves the execution of several tasks, and any of these tasks could fail. When a task fails, the suite is halted and a red icon appears next to the respective task name in the _Cylc_ GUI.
+To investigate the cause of a failure, we can look at the logs `job.err` and `job.out` from the suite run. There are two main ways to do so:
+
+##### Using the _Cylc_ GUI
+Right-click on the task that failed and click on _View Job Logs (Viewer) → job.err_ (or _job.out_).
+To access a specific task, click on the arrow next to the task to extend the drop-down menu with all the subtasks.
+
+
+
+
+##### Through the suite directory
+The suite's log directories are stored in `~/cylc-run/` as `log.`, and the latest set of logs are also symlinked in the `~/cylc-run//log` directory.
+The logs for the main job can be found in the `~/cylc-run//log/job` directory.
+Logs are separated into simulation cycles according to their starting dates, then divided into subdirectories according to the task name. They are then further separated into "attempts" (consecutive failed/successful tasks), where `NN` is a symlink to the most recent attempt.
+
+For the above *Lismore* default example, the `` was set to `1` and no real starting date was used. Since the suite failed, the `job.err` and `job.out` files can be found in the `~/cylc-run//log/job/NN//TASK_NAME/NN` directory.
+
+For a subsequent run, the `` directory gets compressed to `job-.tar.gz` and stored in the `~/cylc-run//log/` directory.
+
+
+
+#### Stop, restart and reload suites
+In some cases, you may want to control the running state of a suite.
+If your _Cylc_ GUI has been closed and you are unsure whether your suite is still running, you can scan for active suites and reopen the GUI if desired.
+To scan for active suites, run:
+```
+cylc scan
+```
+To reopen the _Cylc_ GUI, run the following command from within the [suite directory](#suitedir):
+```
+rose suite-gcontrol
+```
+
+
+##### STOP a suite
+To shutdown a suite in a safe manner, run the following command from within the [suite directory](#suitedir):
+```
+rose suite-stop -y
+```
+Alternatively, you can directly kill the [PBS jobs][PBS job] connected to your run. To do so:
+
+1. Check the status of all your PBS jobs:
+```
+qstat -u $USER
+```
+
+1. Delete any job related to your run:
+```
+qdel
+```
+
+##### RESTART a suite
+There are two main ways to restart a suite:
+
+- **_SOFT_ restart**
+ To reinstall the suite and reopen _Cylc_ in the same state it was prior to being stopped, run the following command from within the [suite directory](#suitedir):
+ ```
+ rose suite-run --restart
+ ```
+
+ !!! warning
+ You may need to manually trigger failed tasks from the _Cylc_ GUI.
+
+
+
+- **HARD restart**
+ To overwrite any previous runs of the suite and start afresh, run the following command from within the [suite directory](#suitedir):
+ ```
+ rose suite-run --new
+ ```
+
+ !!! warning
+ This will overwrite all existing model output and logs for the same suite.
+
+##### RELOAD a suite
+In some cases the suite needs to be updated without necessarily having to stop it (e.g., after fixing a typo in a file). Updating an active suite is called a _reload_, where the suite is _re-installed_ and _Cylc_ is updated with the changes. This is similar to a _SOFT_ restart, except new changes are installed, so you may need to manually trigger failed tasks from the _Cylc_ GUI.
+
+To reload a suite, run the following command from within the [suite directory](#suitedir):
+```
+rose suite-run --reload
+```
+
+#### RAS output files
+
+The RAS output ancillary files can be found in `/scratch/$PROJECT/$USER/cylc-run//share/data/ancils`. The ancillaries are divided for each nested region, with each of the region subdivided in directories named according to the nests names. Therefore, the path of the ancillaries for a specific nest is `/scratch/$PROJECT/$USER/cylc-run//share/data/ancils//`.
+
+
+In addition to the chosen nests, a subdirectory named according to the driving model data can be found within the `nested_region_name` directory.
+The example above has one `nested_region_name` called `Lismore`, with a 2-level nest (2 nests) named `d1000` (outer nest) and `d0198` (inner nest), driven by ERA5 data.
+As a consequence, within the ancillary files directory `/scratch/$PROJECT/$USER/cylc-run//share/data/ancils/` the following folders will be present:
+- `Lismore/d1000`
+- `Lismore/d0198`
+- `Lismore/era5`
+
+The ancillary data files are typically in the [UM fieldsfile](https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_F03.pdf) format.
+
+#### Edit the RAS configuration
+This section describes how to modify the RAS configuration.
+The modifications discussed in this section can change the way the RAS is run and, as a result, control the ancillaries that are generated.
+
+In general, ACCESS modelling suites can be edited either by directly modifying the configuration files within the [suite directory](#suitedir), or by using the [_Rose_ GUI](#rosegui).
+
+!!! warning
+ Unless you are a very expert user, directly modifying configuration files is usually discouraged to avoid incurring in errors.
+
+##### Rose GUI {: id="rosegui"}
+To open the [_Rose_](#rose) GUI, run the following command from within the [suite directory](#suitedir):
+```
+rose edit &
+```
+
+!!! tip
+ The `&` is optional. It allows the terminal prompt to remain active while running the `Rose` GUI as a separate process in the background.
+
+
+##### Change the region centre and name
+{{model}} is a regional model that can perform simulations for a specific region on Earth.
+
+In the RAS, each region can be specified through the following parameters:
+
+- *region centre* → `_rg01_centre_` within the suite.
+ Set of latitude/longitude coordinates defining the centre of the region.
+
+- *nested region name* → `_rg01_name_` within the suite
+ Name for the nested region.
+
+In `{{ras_id}}` these prameters are set by default to the *Lismore Flood* example.
+
+
+
+To change these parameters, edit the `_rg01_name_` and `_rg01_centre_` fields in _suite conf → Regional Ancillary Suite → Nested region 1 setup_, and click the _Save_ button {: style="height:1em"}.
+
+For example, to run an {{ model }} suite for a region with centre (-12.4, 130.8) and name "Darwin":
+
+{: class="example-img" loading="lazy"}
+
+
+
+### Regional Nesting Suite (RNS) {: id="rns"}
+
+The `suite-ID` of the RNS is `{{ rns_id }}`.
+
+
+
+#### Get and run RNS configuration
+Steps to get and run the RNS configuration, as well as monitoring the runs, are analogous to those listed above for the [RAS](#ras).
+The only difference is the `suite-ID` that, for the RNS is `{{ rns_id }}`.
+
+To get the RNS configuration, please follow the steps listed in [Get the RAS configuration](#get-the-ras-configuration), making sure you use the correct RNS `suite-ID` `{{ rns_id }}` when copying the suite.
+
+To run the RNS configuration, please follow the steps listed in [Run the suite](#run-the-suite).
+
+To monitor the RNS suite run, please follow the steps listed in [Monitor the suite runs](#monitor-the-suite-runs).
+
+#### RNS output files
+
+All the RNS output files are available on _Gadi_ inside `/scratch/$PROJECT/$USER/cylc-run/`. They are also symlinked in `~/cylc-run/`.
+
+The RNS output data can be found in the `/scratch/$PROJECT/$USER/cycl-run//share/cycle` directory, grouped for each [cycle](#change-run-length-and-cycling-frequency).
+Within the cycle directory, outputs are divided into multiple nested subdirectories in the format `//`, with [nested_region](), [science_choice]() and [nest_name]() referring to the respective configurable options in the [RAS](#edit-the-ras-configuration).
+
+
+
+Each of the `` directory has the following subdirectories:
+
+- `ics` → initial conditions
+- `lbcs` → lateral boundary conditions
+- `um` → model output data
+
+
+
+The model output data for the `Lismore` `nested_region`, using a `RAL3P2` `science_choice` and `d0198` as a `nest_name`, will be stored in `/scratch/$PROJECT/$USER/cylc-run//share/cycle/20220226T0000Z/Lismore/d0198/RAL3P2/um`.
+
+The RNS atmospheric output data files are typically in the [UM fieldsfile](https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_F03.pdf) format.
+
+#### Edit the RNS configuration
+
+This section describes how to modify the RNS configuration.
+The modifications discussed in this section can change the way the RNS is run, or how its specific [model components] are configured and coupled together.
+
+In general, ACCESS modelling suites can be edited either by directly modifying the configuration files within the suite directory, or by using the [_Rose_ GUI](#rosegui).
+
+!!! warning
+ Unless you are a very expert user, directly modifying configuration files is usually discouraged to avoid incurring in errors.
+
+To open the _Rose_ GUI, you can follow the steps listed in [Rose GUI](#rosegui).
+
+#### Change where the output from run is stored project
+To change where the output from the model run is stored, edit the _NCI_STORAGE_ field in _suite conf → Nesting Suite → General run options _, and click the _Save_ button {: style="height:1em"}.
+
+
+
+#### Change run length and cycling frequency
+The RNS is run in multiple steps, each one constituting a cycle. The job scheduler resubmits the suite every chosen cycling frequency, until the total run length is reached.
+
+For the RNS:
+
+- `CYCLE_INT_HR` is the cycling frequency (in hours)
+- The total run length is the time span between the `INITIAL_CYCLE_POINT` and `FINAL_CYCLE_POINT`
+
+To modify these parameters, navigate to _suite conf → Nesting Suite → Cycling options_, edit the `INITIAL_CYCLE_POINT`, `FINAL_CYCLE_POINT` and the `CYCLE_INT_HR` fields (using [ISO 8601 Duration](https://en.wikipedia.org/wiki/ISO_8601#Durations) format) and click the _Save_ button {: style="height:1em"}.
+
+
+
+
+
+
+
+- [https://nespclimate.com.au/wp-content/uploads/2020/10/Instruction-document-Getting_started_with_ACCESS.pdf](https://nespclimate.com.au/wp-content/uploads/2020/10/Instruction-document-Getting_started_with_ACCESS.pdf)
+- [https://code.metoffice.gov.uk/doc/um/latest/um-training/rose-gui.html](https://code.metoffice.gov.uk/doc/um/latest/um-training/rose-gui.html)
+- [https://opus.nci.org.au/display/DAE/Run+Cylc7+Suites](https://opus.nci.org.au/display/DAE/Run+Cylc7+Suites)
+- [https://opus.nci.org.au/display/Help/Persistent+Sessions](https://opus.nci.org.au/display/Help/Persistent+Sessions)
+
diff --git a/mkdocs.yml b/mkdocs.yml
index 41a9c45d5..ca9af6840 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -101,11 +101,12 @@ nav:
- Models:
- Models: models/index.md
- Model Configurations:
- - Overview: models/configurations/index.md
+ - Supported ACCESS Model Configurations: models/configurations/index.md
# - ACCESS-AM: models/configurations/access-am.md
- ACCESS-CM: models/configurations/access-cm.md
- ACCESS-ESM: models/configurations/access-esm.md
- ACCESS-OM: models/configurations/access-om.md
+ - ACCESS-RAM: models/configurations/access-ram.md
- Model Components:
- Overview: models/model_components/index.md
- Atmosphere: models/model_components/atmosphere.md
@@ -123,6 +124,7 @@ nav:
- Run ACCESS-CM: models/run-a-model/run-access-cm.md
- Run ACCESS-ESM: models/run-a-model/run-access-esm.md
- Run ACCESS-OM: models/run-a-model/run-access-om.md
+ - Run ACCESS-RAM: models/run-a-model/run-access-ram.md
- Modify an ACCESS model's source code: models/run-a-model/build_a_model.md
- Creating Prereleases and Releases for an ACCESS Model: models/run-a-model/create-a-prerelease.md
@@ -12,6 +12,7 @@
@@ -23,6 +24,7 @@
@@ -34,4 +36,16 @@
+ 
+ 
+ 
+ 
+ 