High Resolution Numerical Weather Prediction Project
Website of the ALADIN Consortium
Code Training WW, 9-13 Sept 2019, Toulouse
Article published on 27 June 2019
last modification on 2 July 2019

by Patricia

A WW on "Training on code developments and validation (testing)" will be organised in Toulouse on September 9-12 (poss.13 ?) Sept 2019

 Outline & incentive

The Fortran NWP codes have undergone a fair deep re-factoring since IFS/Arpège CY42. From CY43 until CY46 (and CY47), code rearrangements in order to comply with the needs of the OOPS project, as well as code optimization and specific pruning actions, have changed the “visual outlook” of the common codes. A consequence is that developers, albeit experienced ones, “rediscover”the new codes to some extent, and they face “teething” difficulties for phasing developments from older cycles up to the most recent ones. The goal of the training days is to provide an updated information about the code structure, the specific guidelines for coding in new IFS cycles, and a reviewed vision of “how to think when coding for IFS/Arpège/LAM”.
The working days will focus on the model part (no data assimilation, no surface/SURFEX). Trainees will learn about the renewed (or kept!) code structures in the most recent cycles and solve some problems in this context. Time will be shared between tutorials (talks) and practical exercises.
This training is not intended for absolute beginners, it indeed targets developers with some experience of working with the code and associated tools such as gmkpack.

  Draft content

  • General code overview (re-factoring in recent cycles)
  • About the proper use of GIT-GCO commands
  • Arome aspects: new ICE3, new LIMA, new GFL structures :
  • New model diagnostic outputs
  • How to add a fullpos field
  • How to for dynamics and DDH structures
  • General Fortran optimization aspects
  • Coding and testing for simple precision
  • Elaboration of specific problems / recent examples
  • Mitraillette, checkpack & ciboulette
  • Ideas and evolution towards a renewed validation procedure for code contributions