The Unified Model
Total Page:16
File Type:pdf, Size:1020Kb
NCAS Unified Model Introduction Part I: Overview of the UM system University of Reading, 13-15 April 2016 The Unified Model • The UM is a numerical modelling system, developed by the UK Met Office, and used for operational weather forecasting and climate prediction. • It is licensed to the UK academic community for research. There are also collaborations between the Met Office and the academic community for research and development (e.g. JWCRP, MOAP). • It is used by forecast centres and climate agencies around the world. 2 Seamless modelling • The same core model is used across spatial and temporal scales: – Weather to climate timescales – Global and regional models – High to low resolution (horizontal and vertical) – Various model heights • It can be used in atmosphere only mode, or coupled to: – UM ocean vn6.6.3 or earlier only (e.g. HadGEM2) – NEMO ocean and CICE sea-ice via OASIS coupler – UKCA chemistry and aerosols – JULES land-surface • It can also be used to perform idealised studies, e.g: – Single Column Model (SCM) – Aquaplanet 3 © Crown copyright Met Office 4 Global & regional NWP system Parallel suite 36 Global 17km 70 levels (N768L70) EURO 4km 70 levels UKV 1.5km 70 levels [Retired NAE 12km 70 levels] © Crown copyright Met Office 5 NWP at the Met Office The UM is just one part of a larger forecast system. An example workflow: Academic users can access this data © Crown copyright Met Office 6 Global models • Fixed resolutions: (at mid-latitudes) N48 N96 N144 N216 N320 N512 N768 96 x 73 192 x 145 288 x 217 432 x 325 640 x 481 1024 x 769 1536 x 1152 ~270 km ~135 km ~90 km ~60 km ~40 km ~25 km ~17 km 2.5° x 3.75° 1.88° x 1.25° 1.25° x 0.83° 0.83° x 0.56° 0.56° x 0.38° 0.35° x 0.23° 0.23° x 0.16° • Common scientific configurations used across scales (weather, seasonal and climate): o GA = Global Atmosphere (UM) o GL = Global Land (JULES) o GO = Global Ocean (NEMO) o GSI = Global Sea Ice (CICE) o GC = Global Coupled (all of the above coupled together) • These are ongoing developments with fixed releases. 7 Vertical resolutions Standard resolutions Defined by model levels and height Example: L85 with top at 85 km © Crown copyright Met Office 8 NWP v Climate models NWP Climate Run length 5 day operational forecast, Months (seasonal) 15 day ensemble forecast Years, decades, centuries+ Global resolution Testing: Low resolution: N320 (40 km) with 15 min ts N96 (135 km) with 20 min ts Operational: High resolution: N768 (17 km) with 7.5 min ts N512 (25 km) with 15 min ts Calendar Gregorian Seasonal: Gregorian Other: 360 day Dynamics Non-bit reproducible Bit-reproducible Aerosols Climatological concentrations Interactive schemes with specified. emissions specified (not seasonal). Based on information from Dan Copsey 9 HadGEM2(-ES) Ocean HadGEM2-ES Physical climate biogeochemistry • Full Earth system model • Development completed in 2009 • Used for IPCC AR5 (CMIP5) • N96 – 1° ocean Aerosols and chemistry (UKCA) Interactive vegetation (TRIFFID) Other versions available: Human emissions • -A (atmosphere only) • -AO (coupled atmosphere-ocean) • -CC (carbon-cycle) Earth system minus UKCA 10 HadGEM3(-AO) UM atmosphere (GA) JULES land surface (GL) Under continuous development. There are versions with: • different code releases • different scientific configurations OASIS3 Multiple resolutions: coupler • N96 – ORCA0.25 • N216 – ORCA0.25 NEMO ocean model (GO) CICE sea ice (GSI) • N512 – ORCA0.25 / ORCA12 (experimental) Can run atmosphere-only (Modified from a Met Office diagram.) 11 Other modelling systems • MOGREPS: ensemble forecast – Based on Parallel Suites • Nesting suite: sequence of spatial resolutions • GloSea: seasonal prediction – Based on HadGEM3 • DePreSys: decadal prediction – Based on HadGEM3 (formerly HadCM3) • UKESM(-Hi/Lo): Earth system model – Based on HadGEM3 + submodels – Under development 12 Terminology Model version: defines the code base used. Model configuration: defines the science options, eg GA6.0, GO5.0. Modelling system: application with specific configuration (eg HadGEM3-GC2, GloSea5). Parallel suite: version of operational forecast system Job: particular instance defined and run by user through (UMUI) Experiment: grouping of jobs in UMUI Suite: Rose ‘job’ 13 Major UM developments Old New FCM NEMO & ENDGame Rose Shared dynamics dynamics CICE repositories UM 4.5 UM 5.2 UM 6.1 UM 6.6 UM 7.1 UM 8.5 UM 9.0 UM 10.0 1998 2001 2005 2007 2008 2013 2014 2015 Climate models HadCM3 HadGEM1 HadGEM2 HadGEM3 NWP models PS12 PS19 PS20 … PS34 PS35 PS36 Dynamical core Infrastructure Ocean model 14 UM software (pre vn9.0) PUMA UMUI Database of user jobs FCM Graphical job editor Code manager Compilation and build HPC Atmosphere model OASIS Reconfiguration Dynamical core Coupler Prepares initial Physics model state Diagnostics (STASH) [JULES and/or UKCA] Ocean model Input file tools Output file tools Local / Jasmin Prepare ancillary data Data processing Analysis and visualisation 15 UM software (vn10.0 onwards) PUMA MOSRS UMUI Rose Database of user jobs FCM Graphical job editor Cylc / Rose Code manager Job submission Workflow manager Compilation and build HPC Atmosphere model OASIS Reconfiguration Dynamical core Coupler Prepares initial Physics model state Diagnostics (STASH) [JULES and/or UKCA] Ocean model Input file tools Output file tools Local / Jasmin Prepare ancillary data Data processing Analysis and visualisation 16 NCAS supported machines MOSRS PUMA Code repositories Repositories: Web server (Trac) • Code (UM 10.x) User /home space • Rose suites NOC UMUI, Rose/Cylc and FCM UM submission Lander Rose VM MONSooN Polaris File systems: File systems: /home, /home and /work /projects HPC Wales RDF MASS Jasmin 17 Upcoming UM developments Short-term: • UKESM1 release – Based on GC3 – To include land ice sheets, ocean biogeochemistry, plus carbon and nitrogen cycles Medium term: • N1024 -> N2048 global forecasts Long term: • LFRiC replacement for the UM • GungHo highly scalable dynamical core 18 NCAS Unified Model Introduction Part 2: Running the UM University of Reading, 13-15 April 2016 UM User Interface • The UMUI is a graphical interface to the UM comprising: – Job database (allowing the user to search for and browse jobs). – Window-based job editor (allowing the user to select the code version, scientific configuration and run-time option • The UMUI then creates the scripts and namelists which control the UM run. • It is used for UM versions 4.5 to 8.6. – Later versions use the UMUI replacement Rose. • It is available via the PUMA service, which provides: – All the latest UMUI changes – Centralised access to local files (hand-edits etc) – A common job database for all academic and MONSooN users 20 UMUI vocabulary Experiments: e.g. xxab • A grouping of UM jobs • Identified by a folder icon and description in the UMUI • By default only your own experiments are displayed by the UMUI, although it is possible to search the full database. • Experiments can be created, copied and deleted Jobs: e.g. xxabc • Up to 26 jobs can be grouped in an experiment • Jobs can be created, copied and deleted • 2 jobs can be differenced (if using the same UM version) Navigation window -> input windows • Input panels within a job. • Note that these can very between UM versions. 21 22 Creating a UM job • Choose a UM job from UKMO, NCAS or a colleague that is close to what you wish to run. – Either copy the job into your own job if they are in the same local database, – or upload (import) a basis file (the full description of a UM job which has come from another UMUI database) into your own job. • NCAS standard jobs should be available under the umui owner. • Basis files can be downloaded (exported) from the UMUI and emailed. – Note that additional UMUI files (hand-edits, STASHmasters etc) and data files may also need to be copied to the target system. 23 How UM jobs are defined UM jobs are defined by: • A UM code version (e.g. vn8.2) • Specific UMUI settings (and hand-edits which alter these) • A particular horizontal and vertical resolution • A list of changes to the main code base, in the form of FCM branches. • A defined set of input files: start files, ancillary files and lateral boundary conditions. • STASH items specifying the diagnostic fields to be output (and STASHmaster files which define new diagnostics or alter standard ones). Modelling systems such as HadGEM3 or UKV span different UM versions and have specific “standard jobs” as they develop over time. 24 Submitting a job UM runs are submitted directly from the UMUI. PUMA HPC UMUI scripts (MONSooN/ARCHER) scripts namelists namelists code UM compile, process submit reconfigure & run When a job is processed the UMUI: • Creates the namelists that the UM reads in at runtime. • Generates the scripts used to compile and run the model. When a job is submitted the UMUI: • Starts running the scripts • Copies the namelists and scripts to the HPC • Extracts the code and copies to the HPC 25 Running the UM Three distinct steps (separate batch jobs): • Compilation -> Reconfiguration -> UM atmosphere model run • May also have a Post-processing & archiving step after the run. The compilation is handled by the Flexible Configuration Management (FCM) system which: • manages code components; • creates Makefiles for compilation and loading; • compiles and links the code according to options selected; • creates an executable. The reconfiguration is a stand-alone program which modifies UM atmosphere start files (and ocean files for UM 6.6.3 and earlier). • Compiled with FCM • Runs as a parallel application