Rules of coding are chronologically stored here.
Each is added when there is a significant change to be mentionned to the developers or when a need to precise a specific point is felt .
1. Compilation and modules of interfaces self-generated
2. Reading of NAMELISTS in one time at the beginning
3. Suppression of the allocatable arrays in the time loop of the model
4. Keys of C-precompilation
5. Modifications of the covers files for ECOCLIMAP
6. The DOCTOR norm (from Meso-NH)
7. A few rules for programming (from Meso-NH)
8. A few recommendations from Rimvydas Jasinskas
Try to avoid these: identically named different variables in different modules explicit kinds (except where needed for I/O or computationally sensitive algorithms) tab and non ASCII characters (specially in namelists) pointer like structures in structures (compiler bugs, very hard to debug).
The following few rules are intended for SURFEX developers. They must be seen as a facility to read and update the code more than a constraint. The DOCTOR norm must be respected, following article193. Every routine must include the command IMPLICIT NONE at the beginning, and therefore every (…)
The SURFEX code follows the DOCTOR norm. We only recall the following simple rules for prefixing the variable names :
type status INTEGER REAL LOGICAL CHARACTER TYPE global or MODULE N X L C T dummy arguments K P O H (…)
The mode_cover files are replaced by some ASC/BIN files ( ecoclimapI_covers_param.bin/dat, ecoclimapII_eu_covers_param.bin/dat, ecoclimapII_af_covers_param.bin/dat), with a little program to convert data from one format to the other, convert_ecoclimap_param.f90.
These files are present in (…)
For the different possible types of I/O files:
Until before v7, to manage the types of i/o files not present in certain configurations, some dummy files were needed.
Now, keys of precompilation (1 by type of files) are used.
When, in the code, there is a reference to a particular type of (…)
RSS 2.0
