1 / 14

ICON-LAM Development status, plans and future collaboration within the COSMO consortium

Günther Zängl COSMO-STC, Offenbach, 21.03.2019. ICON-LAM Development status, plans and future collaboration within the COSMO consortium. Outline. DWD-internal transition from COSMO-D2 to ICON-D2: milestones and current status of forecast quality Plans for further development

moshea
Download Presentation

ICON-LAM Development status, plans and future collaboration within the COSMO consortium

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. GüntherZängl COSMO-STC, Offenbach, 21.03.2019 ICON-LAMDevelopment status, plans and future collaboration within the COSMO consortium

  2. Outline • DWD-internal transition from COSMO-D2 to ICON-D2: milestones and current status of forecast quality • Plans for further development • Workflow and organizational aspects

  3. Transition from COSMO-D2 to ICON-D2 Current status • Offline forecasts with initial conditions interpolated from ICON-EU running since summer 2018 • Helped identifying several model deficiencies, most of which have been cured in the meantime • In parallel, experiment suites with full data assimilation coupling have been conducted since autumn 2018 Ongoing work • Online coupling of MEC forward operators to ICON (needed for efficiency reasons; offline coupling was used so far) • Coupling of 3D radar forward operator • Tuning adaptation of latent heat nudging

  4. Transition from COSMO-D2 to ICON-D2 Upcoming milestones • Parallel routine starting in late summer / autumn 2019 • Convening of migration group • Will also serve for providing reforecasts for MOS • Replacement of COSMO-D2 by the end of 2020 • In parallel: development of rapid-update cycle configuration for nowcasting / very short range forecasting • Subsequent slides: Verification scores from preliminary parallel suite for Feb. 19

  5. Surface verification scores for February 2019 ICON-D2 vs. COSMO-D2 bias RMSE Surface pressure 2m temperature 2m rel. humidity

  6. Surface verification scores for February 2019 ICON-D2 vs. COSMO-D2 10m wind speed 10m wind direction 10m hourly gusts

  7. Surface verification scores for February 2019 ICON-D2 vs. COSMO-D2 total cloud cover low cloud cover global radiation

  8. Surface verification scores for February 2019 ICON-D2 vs. COSMO-D2 ETS FBI RR > 0.1 mm/h RR > 2 mm/h RR > 5 mm/h

  9. Plans for further development • Implementation and evaluation of ECRad radiation scheme (ECMWF variant of RRTM scheme with substantial scientific upgrades) • Coupling of ICON with wave model • Usage of more modern / higher resolved external parameter data • Parameterization development: e.g. TOFD scheme, mixed-layer ocean, canopy-layer for TERRA, plus transfer of ongoing COSMO PP/PT outcomes to ICON where possible • Longer-term project: development of a DG-based dynamical core for ICON

  10. ecRad Radiation in ICON-NWP Overview • ecRad[1] is the currently used radiation code in the ECMWF model. • Decision was taken at DWD to evaluate ecRad (4-year post-doc starting in March) • Preparatory work: implementation into ICON (Daniel Rieger) • Flexible and efficient code, continuously developed by Robin Hogan • Different solvers available: McICA, Tripleclouds, SPARTACUS • Gas optical properties provided by RRTM-G, plans to develop a new scheme • High flexibility wrt. clouds: overlap, optical properties, LW-scattering, … • 30-40% faster than previous McRad implementation • Code already has the structure of an external library and was added to ICON build process (with help from Luis and Jan Frederik, thanks!) • Clear interface, e.g., all input wrt. to clouds is passed with an ecrad_cloud object (see next slide) [1] Hogan, R. J., & Bozzo, A. (2018). A flexible and efficient radiation scheme for the ECMWF model. JAMES, 10, 1990–2008. https://doi.org/10.1029/2018MS001364

  11. Interface to ecRad in ICON-NWP mo_ecrad.f90: General interface to all ecrad routines and objects. Only this module has use statements to actual ecrad code mo_nwp_ecrad_init.f90: Setup of ecRad, fill configuration type ecrad_conf with general options (choice of parameterizations, …) mo_nwp_ecrad_interface.f90: Contains interfaces for radiation on full and reduced grid. Current ambient conditions from ICON are passed to ecRad types (e.g., cloud cover to ecrad_cloud) The actual call looks like this (will not change if new fields are added to the types):

  12. First results with ecRad in ICON-NWP (net SW radiation at surface) ecRad-RRTM RRTM R2B5 experiment, full radiation grid, 24h forecast for 25 November 2018, (W m-2) ecRad

  13. Workflow and organizational aspects • COSMO members proposed usage of github or alternatives with comparable functionality to facilitate joint development workflow • Plan: install gitlab server at DKRZ and migrate ICON-internal project management from Redmine to gitlab in order to avoid ‘parallel worlds’ • Discussion: Financial support from COSMO license money possible? • Next slide: proposed technical solution with comments on workflow organization

  14. Illustration of workflow for upcoming collaboration between COSMO consortium and other ICON developer groups

More Related