A "Maintenance Training" took place in Toulouse on September 20-22^th 2010 (see page on aladin website for practical details, agenda, photos, list of participants).
Its objectives were, among others, to help newcomers to get familiar with the phasing procedure, to give them
some overview of the code’s architecture and to explain the coding rules to be respected inside the common
software.

• General presentation of phasing procedure
  • Objectives and generalities about phasing and general description of the phasing roadmap
  • Presentation of GCO’s implication in the phasing and gestion of the code
• Code issues
  • Description of the general architecture of the code
  • Description of different configurations
  • Preprocessing and format of observations for assimilation (Bator, Oulan...)
  • Organization of the time step
  • Variational assimilation: method & technicalities
  • Coding norms and rules (actualized in the framework of OOPS)
  • Development constraints (including presentation of constraints due to shared code with Arp/Ifs)
  • OOPS and basis on object oriented programming
• Presentation of phasing tools
  • ClearCase (View history of modifications, creation of a new branch...)
  • Mitraillette validation’s tool (including experiment on yuki)
  • Execution and validation during phasing (DrHook, output files)
  • Local Validation to the reference, OpenMP, optimization
  • Hirlam experiences on remote maintenance of the code
• Pratical exercices
  • Phasing exercices (including use of clearcase) Olda, Filip, Alena, Karim, Olivier
    • Presentation of gmkpack
    • OpenMP exercices
    • Merging exercices
    • Real case phasing situations
  • Presentation of gmkpack and installation of a cycle (or a subproject) on PC with gmkpack
    Olivier
• Discussion