Changeset f20342a in flex_extract.git for For_developers/Sphinx/source/Documentation/Input/control.rst
- Timestamp:
- May 27, 2020, 8:01:54 PM (4 years ago)
- Branches:
- master, ctbto, dev
- Children:
- 550435b
- Parents:
- a14839a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
For_developers/Sphinx/source/Documentation/Input/control.rst
rb1674ed rf20342a 10 10 11 11 This file is an input file for :literal:`flex_extract's` main script :literal:`submit.py`. 12 It contains the controlling parameters :literal:`flex_extract` needs to decide on dataset specifications,13 handling of the retrieved data and general bahaviour. The naming convention is usually (but not necessary):12 It contains the controlling parameters which :literal:`flex_extract` needs to decide on data set specifications, 13 handling of the data retrieved, and general behaviour. The naming convention is usually (but not necessarily): 14 14 15 15 :literal:`CONTROL_<Dataset>[.optionalIndications]` 16 16 17 The tested datasets are the operational dataset and the re-analysis datasets CERA-20C, ERA5and ERA-Interim.18 The optional extra indications for the re-analysis datasets mark the files for *public users*19 and *global* domain. For the operational data sets (*OD*)the file names contain also information of20 the stream, the field type for forecasts, the method for extracting the vertical coordinate and other things like timeor horizontal resolution.17 There are a number of data sets for which the procedures have been tested, the operational data and the re-analysis datasets CERA-20C, ERA5, and ERA-Interim. 18 The optional indications for the re-analysis data sets mark the files for *public users* 19 and *global* domain. For the operational data sets (*OD*), the file names contain also information of 20 the stream, the field type for forecasts, the method for extracting the vertical wind, and other information such as temporal or horizontal resolution. 21 21 22 22 … … 24 24 ---------------------------------- 25 25 The first string of each line is the parameter name, the following string(s) (separated by spaces) is (are) the parameter values. 26 The parameters can be sorted in any order with one parameter per line.26 The parameters can be listed in any order with one parameter per line. 27 27 Comments are started with a '#' - sign. Some of these parameters can be overruled by the command line 28 28 parameters given to the :literal:`submit.py` script. 29 All parameters have default values . Only those parameters which have to be changed30 mustbe listed in the :literal:`CONTROL` files.29 All parameters have default values; only those parameters which deviate from default 30 have be listed in the :literal:`CONTROL` files. 31 31 32 32 … … 35 35 36 36 A number of example files can be found in the directory :literal:`flex_extract_vX.X/Run/Control/`. 37 They can be used as a template for adaptation s and understand what's possible to38 retrieve from ECMWF's archive.39 For each main dataset there is an example and additionally some variances in resolution, type of field or type of retrieving the vertical coordinate.37 They can be used as a template for adaptation, and to understand what can be 38 retrievee from ECMWF's archives. 39 There is an example for each main data set, and in addition, some more varied with respect to resolution, type of field, or way of retrieving the vertical wind. 40 40 41 41 … … 45 45 ------------ 46 46 The file :literal:`CONTROL.documentation` documents the available parameters 47 in grouped sections with their default values. In :doc:`control_params` you can find a more 48 detailed description with additional hints, possible values and some useful information about 47 in grouped sections together with their default values. 48 In :doc:`control_params`, you can find a more 49 detailed description with additional hints, possible values, and further information about 49 50 the setting of these parameters. 50 51
Note: See TracChangeset
for help on using the changeset viewer.