Banner
GmapDoc website
Slogan du site
Descriptif du site
Technical and coding aspects

The last articles

General Fortran optimizations guide, Dec 2019
Published on 19 August 2020
by Patricia

This document from Ryad El Khatib is the support of a training course of Fortran High Performance omputing for scientists and developers. The purpose of this course is to let developers be aware of the performance traps when they code a piece of scientific software in Fortran.

The expectation (...)

Eradication of arrays bounds violations in IFS/ARPEGE/AROME, August 2019
Published on 26 September 2019
by Patricia

In this note, Ryad explains the origins of the arrays bounds violations issue and proposes a solution to eradicate them. This solution has been implemented in the code (CY47T0).

Cycling in the IFS-ARPEGE-AROME code: a GIT view, April 2019
Published on 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 (...)

GESTION DES NAMELISTS DE MITRAILLETTE, D’OLIVE ET DE L’OPERATIONNEL: CYCLE 46t1r1.
Published on 12 February 2019
by Karim Yessad

RESUME:

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 OLIVE ET VORTEX. Contents / TABLE DES MATIERES:

– 1/ INTRODUCTION.

– 2/ (...)

Library architecture and history of the technical aspects in ARPEGE/IFS, ALADIN and AROME in the cycle 46t1r1 of ARPEGE/IFS.
Published on 12 February 2019
by Karim Yessad

Abstract:

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 the dependencies between the different sub-projects. (...)