Changes between Initial Version and Version 1 of UM/Configurations/UKESM/RelNotes1.0


Ignore:
Timestamp:
08/02/19 15:20:12 (10 months ago)
Author:
jwalton
Comment:

Legend:

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

    v1 v1  
     1= UKESM1 release notes 
     2[[TOC]][[Image()]] 
     3 
     4These are the notes for the first release of the UK Earth System Model (UKESM1).  Some background information on the release and support of UKESM1 is available [https://ukesm.ac.uk/portfolio-item/release-and-support-of-ukesm1/ here] and [https://ukesm.ac.uk/portfolio-item/the-release-of-ukesm1-update/ here].  
     5 
     6== Options for running the model 
     7 
     8By default, the 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:   
     9 
     10 * login node to be used for submission to Met Office HPC: `suite conf -> Machine Options -> MetO Cray login node` 
     11 * Met Office queue to which jobs will be submitted: `suite conf -> Machine Options -> HPC queue`   
     12 
     13Options for specifying the account under which jobs will be run are available in `suite conf -> Project Accounting`: 
     14 
     15 * Select `Use default account` to use the default account for your department.   
     16 * If this is set to `false`, then choose an option from the `Account` menu. 
     17 * If the option is `other`, then enter the account explicitly in `'Other' user account`. 
     18 
     19=== Running on other machines (MONSooN, NEXCS, Archer) 
     20 
     21The 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]).   
     22 
     23To run on Archer, the NERC platform, choose `Archer` for this option and set these `Machine Options`: 
     24 
     25  * `Use Environment Modules` to `Custom module files`  
     26  * `Science Configuration Module Name` to `GC3-PrgEnv/2.0/90386` 
     27  * `Module file location` to `/work/y07/y07/umshared/moci/modules/modules` 
     28 
     29In addition, the following tests (see ([#Testsinthesuite below]) ''must'' be turned off when running on Archer: 
     30   
     31  * `Test restartability` 
     32  * `Test rigorous compiler option` 
     33  * `Test PE decomposition change`  
     34  * `CPMIP Analysis -> CPMIP load balancing analysis` 
     35 
     36When 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`. 
     37 
     38== Using the model in a CMIP6 production run 
     39 
     40Using 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. 
     41 
     42By 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]. 
     43 
     44== Model and suite specifications 
     45 
     46The current version of UKESM1 has an atmospheric resolution of N96 (~140 km) and a one degree resolution in the ocean.  The vertical resolution is 85 levels in the atmosphere and 75 levels in the ocean.   
     47 
     48=== historical, pre-industrial control 
     49 
     50This table lists the UKESM1 suites that are currently available.  There are two fully coupled configurations which each make use of all model components: one with science settings for a historical experiment, and one with settings for a pre-industrial control experiment.    
     51  
     52||=''UM version''=||=''historical''=||=''pre-industrial control''=|| 
     53||=vn11.2=||=[https://code.metoffice.gov.uk/trac/roses-u/browser/b/c/6/1/3/trunk u-bc613]=||=[https://code.metoffice.gov.uk/trac/roses-u/browser/b/c/9/6/4/trunk u-bc964]=|| 
     54 
     55=== abrupt4xCO2, 1%CO2 
     56 
     57Configurations for abrupt4xCO2 and 1%CO2 experiments can be created using the pre-industrial control experiment as a starting point. 
     58 
     59To create a suite for the abrupt4xCO2 experiment, first make a copy of the  [https://code.metoffice.gov.uk/trac/roses-u/browser/b/c/9/6/4/trunk pre-industrial control suite], then in `um -> namelist -> UM Science Settings -> Section 01-02 - Radation -> GAS MMRs`, set `co2_mmr=1.72728e-03`. 
     60 
     61To create a suite for the 1xCO2 experiment, first make a copy of the  [https://code.metoffice.gov.uk/trac/roses-u/browser/b/c/9/6/4/trunk pre-industrial control suite], then in `um -> namelist -> UM Science Settings -> Section 01-02 - Radation -> GAS MMRs -> Varying gas MMRs`, set `l_clmchfcg=.true.` to enable time-varying GHGs.  Finally, in the sub-panel `Varying CO2 MMRs`, set 
     62 
     63{{{ 
     64clim_fcg_levls_co2=4.3182e-04 
     65clim_fcg_nyears_co2=1 
     66clim_fcg_rates_co2=1.0 
     67clim_fcg_years_co2=1849 
     68}}} 
     69 
     70 
     71See [#Sciencenotes below] for more on the science settings of the model. 
     72 
     73== Archiving of duplexed data 
     74 
     75When 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). 
     76 
     77== Compute node usage 
     78 
     79The compute resources used by the suite can be set via controls on the `Machine Options` and `Domain Decomposition` control panels under `suite conf`.  The following discussion is specific to the Met Office HPC for the most part, but may still be helpful for users of other machines. 
     80 
     81The type of compute node can be set via `XC40 core type`: a `Haswell` node has 32 cores, while `Broadwell` has 36.   
     82 
     83On `Domain Decomposition -> Atmosphere`, the number of processes used by the UM can be set via `Atmosphere: Processes East-West` and `Atmosphere: Processes North-South`; additional processes for the IO Server may be requested using `IO Server Processes`.  Finally, `OpenMP threads for the atmosphere` sets the number of threads for each process; multiplying this by the number of processes gives the number of compute tasks.  Using the default values for these parameters, the number of tasks used by the UM is `(32 * 18 + 0) * 2 = 1152`. Dividing by the number of cores per node (in this case `36`) and rounding up (because different executables cannot run on the same node) gives `32` compute nodes used by the atmosphere. 
     84 
     85A similar calculation may be performed for the settings on `Domain Decomposition -> Ocean` using `NEMO: Number of processes East-West`, `NEMO: Number of processes North-South` and `OpenMP threads for the ocean` to give `12 * 9 * 1 = 108` tasks, or `3` compute nodes used by the ocean. 
     86 
     87Finally, on the same control panel, `NEMO: Number of processes in XIOS server` is set to `6`, which equates to `1` compute node used by XIOS.   
     88 
     89Thus, the total number of nodes used by the suite is `32 + 3 + 1 = 36`. 
     90 
     91Changing the number of nodes used by the suite may require load balancing to ensure that HPC resources are being used in the most efficient fashion.  
     92 
     93== Tests in the suite 
     94 
     95The suite contains options for testing different aspects of the model including reproducible restarting, changes in processor decomposition, comparison to known good output and integrity of archived files.  Some of these tests may be of more interest to developers than general users of the model; they can be turned on or off via the `suite conf -> Testing` control panel. 
     96 
     97=== Testing for PE decomposition change 
     98 
     99Changing the PE decomposition will change the results of the model because of the behaviour of the chemistry solver within the UM. Thus, by default, the `Test PE decomposition change` test (see `suite conf -> Testing`) will fail, and so this test has been turned off. There is a version of the chemistry solver which does not change results; this can be selected by setting `l_ukca_asad_columns=.true.` in `app/um/rose-app.conf`. With this option selected, the PE decomposition change test should pass.  
     100 
     101Note that we do not select this version of the chemistry solver by default because it has a performance overhead; specifically, it causes an atmosphere-only job to run about 10% slower than when running with `l_ukca_asad_columns=.false.`. 
     102 
     103It should be noted that changing the PE decomposition for the ocean in UKESM will also change results because this changes results for both the iceberg code in NEMO and for the CICE code. This behaviour cannot be rectified by setting a single variable (that is, there is no analogue of `l_ukca_asad_columns` for NEMO and CICE).  
     104 
     105== Science notes 
     106 
     107The historical release job differs from the first member of the CMIP6 historical ensemble (`u-bb075`) in the following ways: 
     108* The anthropogenic SO2 emission ancillaries were produced using different methodologies. The resulting SO2 emission in the model is nearly identical but has differences at the bit level. 
     109* It includes a fix for the aerosol plume scavenging diagnostic 38900-38932 to ensure that they bit-compare across differing processor decompositions. The difference appears at only a small number of points where the value is very close to zero. 
     110 
     111The piControl release job differs from the CMIP6 piControl run (`u-aw310`) in the following ways: 
     112* The anthropogenic emission height is different. In the release job all anthropogenic SO2 is emitted at the surface, consistent with the model's treatment of other anthropogenic emissions (except NOx emissions from aircraft which are supplied with a vertical emission profile). In the CMIP6 piControl, around 30% of anthropogenic emissions were released at 500m. Because the 1850 anthropogenic emissions are tiny relative to natural emissions from volcanoes and the ocean, this difference in emission height makes no meaningful difference to the SO2 burden or the aerosol simulation. 
     113* The release job includes several diagnostic fixes which were not included in the CMIP6 piControl run. These include: 
     114   a. The fix to plume scavenging diagnostics described above 
     115   b. Corrections to diagnostics 30312, 30313, 30298 which were corrupted in the CMIP6 piControl 
     116   c. Addition of some other diagnostics to CMIP6 PP streams 
     117 
     118== Known issues 
     119 
     120(none) 
     121 
     122== Support 
     123 
     124* Met Office users running this suite on Met Office machines (Met Office HPC, MONSooN) should contact Jeremy Walton (jeremy.walton@metoffice.gov.uk). 
     125 
     126* NERC users requiring assistance running this suite on NERC machines (ARCHER, NEXCS, MONSooN) should raise a ticket on the NCAS-CMS helpdesk at http://cms.ncas.ac.uk/wiki/CmsHelpdesk.   
     127 
     128* Users running this suite on other machines should contact local support services.  
     129 
     130''Last modified on [[LastModified]] by [[LastModifiedBy]]''