Changes between Version 7 and Version 8 of UM/Configurations/UKESM/RelNotes1.0
- Timestamp:
- 14/02/19 17:49:01 (10 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UM/Configurations/UKESM/RelNotes1.0
v7 v8 58 58 To run on MONSooN, the Met Office / NERC collaborative platform, set `suite conf -> Machine Options -> Site at which model is being run` to `MONSooN`. 59 59 60 Output files created by the suite running on MONSooN may be archived to tape via MOOSE. The options for requesting this can be found under the `postproc -> Post Processing - common settings` control panel. Set `archive_command` to `Moose` and provide (or check) values for further options in the subpanel `Moose Archiving`. See [#Archivingofduplexeddata below] for more on the `non_duplexed_set` option. 61 60 62 ==== NEXCS 61 63 62 64 To use NEXCS, the NERC-only share of MONSooN, set `suite conf -> Machine Options -> Site at which model is being run` to `MONSooN` and select a NEXCS account for running jobs (see [#Optionsforrunningthemodel above]). 63 65 64 When running on NEXCS, the output files created by the suitemay 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.66 Output files created by the suite running on NEXCS 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 67 66 68 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`. … … 84 86 * `CPMIP Analysis -> CPMIP load balancing analysis` 85 87 86 When running on Archer, the output files created by the suitemay 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.88 Output files created by the suite running on Archer 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 89 88 90 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`.