1 / 4

OES Requirements

OES Requirements. Coupled modelling Rationale outlined by Prof. Drijfhout. Will use HadGEM3 → UKESM1 Hence both components as benchmarks (but not the full UM). Also coupled & Earth System models for multi-millennial simulations : GENIE, FAMOUS OES Physical Oceanography

olaf
Télécharger la présentation

OES Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OES Requirements Coupled modelling Rationale outlined by Prof. Drijfhout. Will use HadGEM3 → UKESM1 Hence both components as benchmarks (but not the full UM). Also coupled & Earth System models for multi-millennial simulations: GENIE, FAMOUS OES Physical Oceanography New recruits, all requiring significant HPC A variety of topics: changing water cycle, iceberg modelling, anthropogenic CO2 uptake, North Atlantic seasonal climate predictability, building ocean climate change scenarios, etc. Models used: NEMO, MITgcm, WaveWatch III. Increasing use of ensemble modelling. OES PhD students Heavy use of MITgcm & low-resolution NEMO, + OtisMPI (tidal) Currently hamstrung by lack of cores (384 active cores) in Nautilus Want an easy to use system, from which they can easily trade up to e.g. Iridis4. Helpful to use same system as their mentors. Important to develop highly values skills, on a “mainstream” system.

  2. Scheduling/accounting: a) Fair play between funding partners: How will this be measured?, Need archive of job stats, to be analysed as required by management, b) Hope to run ensemble jobs: many jobs of modest size Want this to be convenient for the users, and easy to schedule to fill “spare” capacity c) Controllable by NOC-S IT staff without much staff overhead, d) Focus on jobs of 128-256 cores (ideally want several such jobs at a time)

  3. Possible usage (OES): 1. NEMO simulations with ORCA025 on 200+ cores 2. ORCA1 with Medusa on ~100 cores 3. Large ensembles at coarse resolution (e.g. ORCA2) on 200+ cores 4. HadGEM3 with ORCA025 on 500+ cores 5. HadGEM3 with ORCA1 and Biogeochemistry on 100+ cores 6. Wavewatch III on 200+ cores 7. Idealised studies with NEMO and MITgcm on up to 200+ cores 8. Large ensembles with GENIE, HadCM3 and FAMOUS on up to 100+ cores . 9. PhD students running projects varying from 10 to 200+ cores. 10. OES geophysicists running various models on 10-100+ cores

  4. Possible usage (NERC): 1. NEMO simulations with ORCA1 and ORCA025 on up to 200+ cores, including ensembles 2. NEMO-MEDUSA simulations with ORCA1 and ORCA025 on up to 400+ cores 3. HadGEM3/ UKESM1 with ORCA1 and ORCA025 ocean on up to 500+ cores 4. Test NEMO simulations with ORCA0083 (1/12°) on up to 1500 cores 5. Idealised gyre-scale simulations with NEMO using ORCA1, ORCA025, ORCA0083 on up to 200+ cores 6. Runs with alternative ocean models (e.g. ocean-only and coupled HyCOM/ CHIME, MITgcm) on up to 200+ cores if funded externally 7. PhD student projects running on up to 200+ cores.

More Related