GmapDoc website
Home > Specific documentation > Technical and coding aspects > Coding, phasing, porting > Coding, phasing, porting

Coding, phasing, porting

Before actually acceding the documents of this sub-section, we advise any newcomer to first consult the two basics:

The content of this Coding, Phasing and Porting devoted sub-section is highly recommended for anybody who wishes to get familiar with tools and methodologies for the upgrade and validation of the NWP code.
Reading most of the present notes hopefully provides a good kick-off for future phasers coming to Toulouse.
The documentation describes the source code norms, Meteo-France’s repository systems (clearcase then GIT),
tools for compilation (gmkpack) and validation (mitraillette). Other documents concern namelists and code architecture.
A "phasing roadmap" lists the sequence of tasks to be performed during one given phasing exercise in GMAP.

For more home reading, one can browse through some of the notes about I/O in the files and data section and the "galaxy"
of configurations document in the Configurations section.

Very detailed, but fairly specialized, documentation about code aspects can be found in the Technical Aspects section.

Articles in this section


Cycling in the IFS-ARPEGE-AROME code: a GIT view, April 2019 (Coding, phasing, porting)

Wednesday 17 April 2019 by Patricia
The diagram prepared by Alexandre Mary illustrates the evolution of cycles in the common code IFS-ARPEGE-AROME in the GIT repository of Meteo-France. Main features to remember: all the main cycles (e.g. CY43T2, CY46) are tags on the master branch. a T cycle (e.g. CY47T1) is constructed as a (...)


Library architecture and history of the technical aspects in ARPEGE/IFS, ALADIN and AROME in the cycle 46t1r1 of ARPEGE/IFS. (Coding, phasing, porting)

Tuesday 12 February 2019 by Karim Yessad
Sommaire Abstract RESUME Contents This documentation has the aim to give a general overview of the library architecture ARPEGE/IFS, ALADIN and AROME models. Information will be given about an historical overview of the most important code rewritings, and about (...)


GESTION DES NAMELISTS DE MITRAILLETTE, D’OLIVE ET DE L’OPERATIONNEL: CYCLE 46t1r1. (Coding, phasing, porting)

Tuesday 12 February 2019 by Karim Yessad
Sommaire RESUME Contents / TABLE DES MATIERES CETTE DOCUMENTATION EST UN MEMORANDUM RECAPITULANT LES PRINCIPALES ACTIONS A EFFECTUER CONCERNANT LA MAINTENANCE DES NAMELISTS DE ``MITRAILLETTE", AINSI QUE CELLES DE L’OPERATIONNEL, QUI VONT DANS LES ENVIRONNEMENTS (...)


MITRAILLETTE: ENVIRONNEMENT FILES AND USER’S GUIDE. VERSION v122018. (Coding, phasing, porting)

Thursday 20 December 2018 by Karim Yessad
Sommaire Abstract Contents MITRAILLETTE is a software designed to do some basic validations on ARPEGE, ALADIN, AROME, and versions used by ALADIN or HIRLAM partners. It is shared between METEO-FRANCE, ALADIN partners and HIRLAM partners. It is currently not (...)


ORGANISATION DES DONNEES, ET LEUR INITIALISATION, DANS ARPEGE/IFS: CYCLE 45T1. (Coding, phasing, porting)

Wednesday 25 October 2017 by Karim Yessad

CETTE DOCUMENTATION DONNE QUELQUES BASES SUR L’ORGANISATION DES DONNEES DANS ARPEGE/IFS, NOTAMMENT EN RELATION AVEC OOPS, ET L’ORDRE DANS LEQUEL ON INITIALISE LES DIFFERENTS OBJETS.



Meteo-France’s GIT toolbox: GIT-tools (Coding, phasing, porting)

Wednesday 7 September 2016 by Patricia
Sommaire GIT-GCP toolbox for Toulouse Upgrade of GIT-GCO toolbox This document by Claude Fischer introduces the GIT toolbox, developed at Meteo-France (MF) and used since CY39T1/CY40 as Source Code Repository (SCR) in Toulouse. Therefore, these GIT-tools also (...)


GMKPACK documentation or Getting started with gmkpack : environment to compile and make binaries (Coding, phasing, porting)

Wednesday 18 June 2014
This document has been written in order to help people to use the procedure gmkpack with a manual and a tutorial. In June 2014, It is the version 6.6.0. gmkpack is a procedure that has been written by GCO and Ryad El Khatib in order to create an environment to compile and make binaries from (...)


OOPS C++ Coding Guidelines (2013) (Coding, phasing, porting)

Wednesday 6 March 2013 by Patricia
This document " OOPS C++ Coding Guidelines was elaborated by Yannick Tremolet and the team of the OOPS technical review. The following guidelines are based on a draft document from Baudouin Raoult, and were updated following the OOPS code review 11-15 July (...)


Coding standards for ARPEGE, IFS and ALADIN Systems (Nov. 2011) (Coding, phasing, porting)

Monday 28 November 2011 by Patricia
This document summarizes the most important coding norms and rules one has to keep in mind while designing and writing a piece of code in the Arpège-IFS software : Standards for the presentation of the code Preliminary design of the code Detailed design of the code Detailed Fortran coding (...)


Pour une meilleure gestion des namelists et des validations (Juin 2010). (Coding, phasing, porting)

Monday 13 September 2010 by Karim Yessad
Sommaire RESUME TABLE DES MATIERES ON RECENSE ICI LES RAISONS QUI ONT CONDUIT DANS LE PASSE A DES DIFFICULTES DE VALIDATIONS, ET ON PROPOSE UN CERTAIN NOMBRE DE RECOMMANDATIONS AFIN D’AMELIORER LA VALIDATION DES CODES ET D’Y PASSER UN PEU MOINS DE TEMPS. (...)


Home | Contact | Site Map | | Site statistics | Visitors : 231475

Follow site activity en  Follow site activity Specific documentation  Follow site activity Technical and coding aspects  Follow site activity Coding, phasing, porting   ?    |    titre sites syndiques OPML   ?

Site powered by SPIP 3.2.4 + AHUNTSIC

Creative Commons License