Changes between Version 81 and Version 82 of Documentation/Forcings
- Timestamp:
- 2018-02-28T11:50:25+01:00 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Documentation/Forcings
v81 v82 56 56 A longer discussion on the differences between the two drivers (dated in 2016) can be found on https://forge.ipsl.jussieu.fr/orchidee/wiki/Branches/Driver_Improvements. 57 57 58 (c) '''Usually, the forcing files are stored in the shared accounts''' in IGCM/SRF/METEO directory. The shared accounts are found: 58 (c) '''Adding the cell_method attribute to files'''. 59 It is a good practice to add the cell_method attribute to each of the forcing variable in order to document how they relate to the time axis. This attribute will say if the variable represents a point in time (instantaneous) or averages an interval (). Furthermore it can inform how the time interval over which the variable is valid relates to the discrete points in time the axis provides. 60 The general form of the attribute follows the CF convention and is "cell_method = axname : method(position)" where the folowing values can be inserted : 61 * '''axname : ''' 62 * '''method :''' 63 * '''position :''' 64 65 (d) '''Usually, the forcing files are stored in the shared accounts''' in IGCM/SRF/METEO directory. The shared accounts are found: 59 66 * At TGCC: /ccc/work/cont003/dsm/p86ipsl/IGCM 60 67 * At IDRIS: … … 70 77 Read more about the shared accounts and IGCM repository here [http://forge.ipsl.jussieu.fr/igcmg_doc/wiki/DocBenvEcommonfiles] 71 78 72 ( d) '''Tips and script examples when building/using meteorological forcing files''':79 (e) '''Tips and script examples when building/using meteorological forcing files''': 73 80 * '''Land compressed files''': 74 81 - The spatial structure of ORCHIDEE forcing files can either be 2D, or 1D if we exclude the sea points to construct a vector of land points. In both cases, this imposes a land-sea mask, to define the land points on which ORCHIDEE will run if we use 2D files, or to construct the 1D files. In the latter case, the landpoint indices are initialized in the NW corner, and increase for each land point encountered when scanning the 2D array from W to E then from N to S.