GmapDoc website

IO IN THE CYCLE 45 OF ARPEGE/IFS: CALL-TREE ASPECTS.

Thursday 29 June 2017 by Karim Yessad
  Table of contents  

 Abstract:

This documentation gives an overview of the IO (file reading and writing) done in the most usual configurations. This is not a technical documentation about IO but rather a documentation describing entries to IO routines. It is not a comprehensive documentation for all configurations but sticks to the main configurations used for example in the MF operational suite. When locating file reading and writing in the code one has realized that this is not so easy to find where these IO are done in the code. The aim of this documentation is more precisely to give, for a subset of configurations, the list of files read and written, where they are read or written in the code, the local name of the file and the logical unit involved.


 RESUME:

CETTE DOCUMENTATION DONNE UNE VISION DES ENTREES-SORTIES (LECTURE ET ECRITURE SUR FICHIERS) FAITES DANS LES CONFIGURATIONS LES PLUS UTILISEES. CE N’EST PAS UNE DOCUMENTATION TECHNIQUE SUR LES IO MAIS PLUTOT UNE DOCUMENTATION DONNANT LES POINTS D’ENTREE AUX ROUTINES LISANT OU ECRIVANT DES FICHIERS. CE N’EST PAS UNE DOCUMENTATION DETAILLEE POUR TOUTES LES CONFIGURATIONS; ELLE S’EN TIENT AUX PRINCIPALES CONFIGURATIONS UTILISEES PAR EXEMPLE DANS L’ENVIRONNEMENT OPERATIONNEL A METEO-FRANCE. RECHERCHER L’EMPLACEMENT DES LECTURES-ECRITURES SUR FICHIERS DANS LE CODE N’EST PAS VRAIMENT AISE. LE BUT DE CETTE DOCUMENTATION EST PLUS PRECISEMENT DE DONNER, POUR UN CERTAIN JEU DE CONFIGURATIONS, LA LISTE DES FICHIERS LUS ET ECRITS, QUELLE PARTIE DE CODE LES LIT OU LES ECRIT, LE NOM LOCAL DES FICHIERS ET LE NUMERO DE LEUR UNITE LOGIQUE.


 Contents:

  • 01/ Introduction and purpose.
  • 02/ Routines doing file reading/writing.
  • 03/ ARPEGE configuration 1 with real data, no initialisation, with historical files writing (containing CFU and XFU fields).
  • 04/ ALADIN or AROME configuration 1 with real data, no initialisation, with historical files writing (containing CFU and XFU fields).
  • 05/ ARPEGE configuration 1 with real data, no initialisation, reading and writing restart files.
  • 06/ ARPEGE configuration 1 with real data doing DFI initialisation (LDFI=T).
  • 07/ Off-line FULL-POS configuration with departure and arrival climatologies.
  • 08/ ARPEGE configuration 1 with real data, no initialisation, with in-line FULL-POS configuration with departure and arrival climatologies.
  • 09/ ARPEGE configuration 1 with real data, no initialisation, and screening.
  • 10/ ARPEGE configuration 1 with real data, no initialisation, and trajectory update.
  • 11/ LTRAJHR=F incremental 4D-VAR minimisation (configuration 131).
  • 12/ LTRAJHR=T incremental 4D-VAR minimisation (configuration 131).
  • 13/ ARPEGE configuration 801 with real data used for sensitivity studies.
  • 14/ ARPEGE configuration 601 with real data like the MF-PEARP one.
  • 15/ ARPEGE configuration 701 with real data for CANARI surface assimilation (cf. MF operational suite, LAEINC=T).
  • 16/ ARPEGE configuration 901 to convert ECMWF MARS files into MF ARPEGE files.
  • 17/ Configuration to provide dilatation/contraction matrices.
  • 18/ ARPEGE configuration 923 to provide climatological files (MF only).
  • 19/ ARPEGE configuration 931 to provide SST files.
  • 20/ ARPEGE configuration 932 to provide ice content files.
  • 21/ References and internal notes.

titre documents joints

Version cycle 45

29 June 2017
info document : PDF
223.9 kb

Version cycle 44

7 March 2017
info document : PDF
223.8 kb

Version cycle 43

25 February 2016
info document : PDF
223.1 kb

Version cycle 42

7 July 2015
info document : PDF
221.8 kb

Version cycle 41t1

17 March 2015
info document : PDF
221.8 kb

Home | Contact | Site Map | | Site statistics | Visitors : 1553 / 192290

Follow site activity en  Follow site activity Specific documentation  Follow site activity Files and data   ?    |    titre sites syndiques OPML   ?

Site powered by SPIP 3.0.26 + AHUNTSIC

Creative Commons License