| 54 | | The model may be run on other machines, which can be selected via `suite conf -> Machine Options -> Site at which model is being run`. Thus, to run on MONSooN, the Met Office / NERC collaborative platform, choose `MONSooN` for this option. To use NEXCS, the NERC-only share of that machine, choose `MONSooN` and select a NEXCS account (see [#Optionsforrunningthemodel above]). |
| | 54 | The model may be run on other machines, which can be selected via the option `suite conf -> Machine Options -> Site at which model is being run`. See [wiki:UKESM/UKESM1intro#Backgroundandprerequisites here] for more available resources and how to access them. More specific instructions for suite settings are in the following subsections. |
| | 55 | |
| | 56 | ==== MONSooN |
| | 57 | |
| | 58 | To run on MONSooN, the Met Office / NERC collaborative platform, choose `MONSooN` for this option. |
| | 59 | |
| | 60 | ==== NEXCS |
| | 61 | |
| | 62 | To use NEXCS, the NERC-only share of MONSooN, choose `MONSooN` for this option, and select a NEXCS account for running jobs (see [#Optionsforrunningthemodel above]). |
| | 63 | |
| | 64 | When running on NEXCS, the output files created by the suite may be archived to disk. The options for requesting this can be found under the `postproc -> Post Processing - common settings` control panel. Set `archive_command` to `NEXCS` and provide values for `archive_root_path` and `archive_name` in the subpanel `Archer Archiving` (sic) to specify the location of the archived files on NEXCS. |
| | 65 | |
| | 66 | Following archiving, the files may be optionally transferred to a remote machine such as JASMIN. Provide values for `remote_host` (the address of the remote machine) and `transfer_dir` (the location of the archived files on the remote machine) in the subpanel `JASMIN Transfer`. In addition, transferring must be turned on by setting `suite conf -> Build and Run -> PP Transfer` to `true`. |
| | 67 | |
| | 68 | Note that, before transfer from NEXCS to JASMIN can work, some setup of communications is required - see [wiki:Docs/PostProcessingAppNexcsSetup#sshjasmin here] for more details. |
| | 69 | |
| | 70 | ==== Archer |
| 70 | | When running on Archer, the output files created by the suite may be archived to disk and, optionally, transferred to a remote machine such as JASMIN. The options for requesting this can be found under the `postproc -> Post Processing - common settings` control panel. Set `archive_command` to `Archer` and provide values for `archive_root_path` and `archive_name` in the subpanel `Archer Archiving`. The subpanel `JASMIN Transfer` contains options for transferring the output; in addition, `suite conf -> Build and Run -> PP Transfer` must be set to `true`. |
| | 86 | When running on Archer, the output files created by the suite may be archived to disk. The options for requesting this can be found under the `postproc -> Post Processing - common settings` control panel. Set `archive_command` to `Archer` and provide values for `archive_root_path` and `archive_name` in the subpanel `Archer Archiving` to specify the location of the archived files on Archer. |
| | 87 | |
| | 88 | Following archiving, the files may be optionally transferred to a remote machine such as JASMIN. Provide values for `remote_host` (the address of the remote machine) and `transfer_dir` (the location of the archived files on the remote machine) in the subpanel `JASMIN Transfer`. In addition, transferring must be turned on by setting `suite conf -> Build and Run -> PP Transfer` to `true`. |
| | 89 | |
| | 90 | Note that, before transfer from Archer to JASMIN can work, some setup of communications (specifically, ''both'' [wiki:Docs/PostProcessingAppArcherSetup#sshpumatodtn between PUMA and Archer data transfer node], ''and'' [wiki:Docs/PostProcessingAppArcherSetup#sshdtntojasmin between Archer data transfer node and JASMIN]) is required. |
