The configurations listed here are those that are currently considered 'core' by the JULES management and science committees.
Source / Suite ID
The UK Earth System Model
Get suite IDs Rosie Go by searching for "UKESM1" or "JULES-ES".
JULES-ES is the standalone version of the UKESM configuration. JULES-ES is the current configuration used in the CMIP6 Earth System setup and supercedes:
- JULES-C (the original 'carbon cycle' config)
- JULES-C-1p1 (JULES-C with an improved seasonal cycle)
- JULES-CN (JULES-C-1p1 with the new soil biogeochemistry model)
Global Land vn7.0 (GL7.0)
For coupled runs (i.e. used in conjunction with the Global Atmosphere (GA) configuration), see website for suite IDs or search Rosie Go for "GL7.0".
Some suite numbers are now listed here.
GL is a configuration of JULES being developed by the UKMO and John Edwards (see Walters et al. 2014, Walters et al. 2017 and this table of Rose suites). GL7.0 is the current configuration used in the CMIP6 Physical Model setup
For the latest on GL9.0 see here.
Operational global NWP forecast
General info here.
Search Rosie Go.
Operational UK Variable-resolution (UKV) forecast
Search Rosie Go.
Note: From page 29 and fig 19 of Lock-et-al-2016-DiurnalKD16_v1.compressed.pdf regarding canopy height, UKV now requires all C3 grass to be 1.46 m tall (although this is currently being reviewed).
Note that inclusion in these tables is not intended to mean a configuration is necessarily 'recommended' for your particular use of JULES: these are configurations that have been tried and tested in particular situations and therefore should be consistent and accurate in those contexts, but you will have to assess for yourself whether it is suitable for your application of JULES. For example, in many operational configurations intended for the UM configurations are optimised for best results across ocean and sea ice surfaces as well as land surface, which means that they may not be as optimal as other configurations for land-only runs.
n.b. Because of the greater testing requirements for coupled configurations, and therefore correspondingly longer lead times for version releases, offline model setups will usually include more up-to-date science than their closest coupled counterparts. For benchmarking tests for some of these configurations, see the evaluation page.