Changes between Version 4 and Version 5 of UM/Configurations/UKESM/RelNotes1.0/AMIP


Ignore:
Timestamp:
28/03/19 14:21:53 (6 months ago)
Author:
jwalton
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UM/Configurations/UKESM/RelNotes1.0/AMIP

    v4 v5  
    1919== Options for running the model 
    2020 
    21 By default, each UKESM1 suite is set up to run the model on the Met Office HPC.  The suite offers several options for specifying how the model is to be run, including:   
     21By default, each UKESM1 suite is set up to run the model on the Met Office HPC (i.e. `suite conf -> Host Machine -> Site at which model is being run` is set to `MetO Cray ('meto_cray')`).   
     22 
     23The suite offers several further options for specifying how the model is to be run, including:   
    2224 
    2325 * login node to be used for submission to Met Office HPC: `suite conf -> Host Machine -> Compute Host` 
     
    7274Using 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. 
    7375 
    74 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]. 
     76By 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).  More information on setting up a CMIP6 experiment is available [https://code.metoffice.gov.uk/trac/ukcmip6/wiki/ExperimentGuidance here on the MOSRS]. 
    7577 
    7678== Archiving of duplexed data 
    7779 
    78 When running on Met Office machines (including Monsoon), the suite will, by default, archive ''a single copy'' of its data to MOOSE.  For critical model runs, this setting may be changed to archive two copies of the data (i.e. duplex) by switching `non_duplexed_set` in `postproc -> Post Processing-common settings -> Moose Archiving` to `false`.  Further guidance on when to choose this option is available at http://www-twiki/Main/MassNonDuplexPolicy (note that this link only works from within the Met Office). 
     80When running on Met Office machines (including Monsoon), the suite will, by default, archive ''a single copy'' of its data to MOOSE.  For critical model runs, this setting may be changed to archive two copies of the data (i.e. duplex) by turning on  `Duplex dataset archiving` in `suite conf -> Host Machine`.  Further guidance on when to choose this option is available at http://www-twiki/Main/MassNonDuplexPolicy (note that this link only works from within the Met Office). 
    7981 
    8082== Tests in the suite