LMDZ Coding conventions and guidelines
De LMDZPedia
Révision de 24 janvier 2025 à 17:39 par Lfairhead (discussion | contributions) (Page créée avec « == Generalities == * fortran keywords in fortran files will be in UPPER case == Naming of modules == Module names should have a '''lmdz_''' prefix. For example, the fi... »)
Generalities
- fortran keywords in fortran files will be in UPPER case
Naming of modules
Module names should have a lmdz_ prefix. For example, the file lmdz_wave.F90 would be a module containing one or more subroutines:
1 MODULE lmdz_wave
2 IMPLICIT NONE
3
4 CONTAINS
5
6 SUBROUTINE wave_init (...)
7 ...
8 END SUBROUTINE wave_init
9
10 SUBROUTINE wave_calc (...)
11 ...
12 END SUBROUTINE wave_calc
13
14 END MODULE lmdz_wave
Beware: the renaming of already existing parametrization modules (to the lmdz_ format) should only occur once they have been re-written to adhere to the coding conventions for parametrizations (see below) as we use it as a marker that the recoding work on that particular parametrization has been done.
Coding conventions for parametrizations
Following different discussions among LMDZ developpers (summarized in one of our weekly meetings here, the following coding rules apply to the development of LMDZ parametrizations: