Changes between Version 8 and Version 9 of UM/Configurations/UKESM/RelNotes1.0

Timestamp:

15/02/19 11:51:45 (6 months ago)

Author:

jwalton

Comment:

—

UM/Configurations/UKESM/RelNotes1.0

@@ -10 +10 @@
 The model is distributed and run as a [wiki:RoseCylc Rose] suite.  A number of different configurations of the model are available, described in the following subsections.  
 
-''Note that links to suites require access to the Met Office Science Repository Service - see [wiki:UKESM/UKESM1intro#Backgroundandprerequisites here] for more details''.
+''Note that links to suites (and to a couple of other pages) require access to the Met Office Science Repository Service (MOSRS) - see [wiki:UKESM/UKESM1intro#Backgroundandprerequisites here] for more details''.
 
 === historical, pre-industrial control
@@ -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`.  
 
-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. 
+Output files created by the suite running on MONSooN may be archived via the Met Office Operational Storage Environment (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. 
+
+Note that you must have a MOOSE account before archiving can work - see [#Support below] for help. 
 
 ==== NEXCS
@@ -94 +96 @@
 == Using the model in a CMIP6 production run
 
-Using the model in a CMIP6 production run requires the provision of extra information (for example, the MIP and the experiment to which the run is contributing).  This information must be specified in the suite, and the suite will check its validity.  See [https://code.metoffice.gov.uk/trac/ukcmip6/wiki/CMIP6/RoseSuiteMetadata here] for more details about this information.
+Using the model in a CMIP6 production run requires the provision of extra information (for example, the MIP and the experiment to which the run is contributing).  This information must be specified in the suite, and the suite will check its validity.  See [https://code.metoffice.gov.uk/trac/ukcmip6/wiki/CMIP6/RoseSuiteMetadata here on the MOSRS] for more details about this information.
 
-By default, the suite is ''not'' set up to run in full CMIP6 production mode, so this information is not required.  To change this, set `suite info -> project` to `u-cmip6` (which will expose the interface in `suite info` for collecting this information) and set `suite conf -> Project Accounting -> CMIP6 Experiment` to `true` (which will turn on the validation of the information).  More information on setting up a CMIP6 experiment is available [https://code.metoffice.gov.uk/trac/ukcmip6/wiki/ExperimentGuidance here].
+By default, the suite is ''not'' set up to run in full CMIP6 production mode, so this information is not required.  To change this, set `suite info -> project` to `u-cmip6` (which will expose the interface in `suite info` for collecting this information) and set `suite conf -> Project Accounting -> CMIP6 Experiment` to `true` (which will turn on the validation of the information).  More information on setting up a CMIP6 experiment is available [https://code.metoffice.gov.uk/trac/ukcmip6/wiki/ExperimentGuidance here on the MOSRS].
 
 == Archiving of duplexed data