Ignore:
Timestamp:
May 27, 2020, 8:01:54 PM (4 years ago)
Author:
Petra Seibert <petra.seibert [at) univie.ac.at>
Branches:
master, ctbto, dev
Children:
550435b
Parents:
a14839a
Message:

Language corrections for the Sections Developers, Support, Changelog, and the home directory (index.html)

further improvment of documentation, close to final

File:
1 edited

Legend:

Unmodified
Added
Removed
  • For_developers/Sphinx/source/Documentation/Input/control.rst

    rb1674ed rf20342a  
    1010 
    1111This 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):
     12It contains the controlling parameters which :literal:`flex_extract` needs to decide on data set specifications,
     13handling of the  data retrieved, and general behaviour. The naming convention is usually (but not necessarily):
    1414
    1515   :literal:`CONTROL_<Dataset>[.optionalIndications]`
    1616
    17 The tested datasets are the operational dataset and the re-analysis datasets CERA-20C, ERA5 and 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 datasets (*OD*) the file names contain also information of
    20 the stream, the field type for forecasts, the method for extracting the vertical coordinate and other things like time or horizontal resolution.
     17There 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.
     18The optional indications for the re-analysis data sets mark the files for *public users*
     19and *global* domain. For the operational data sets (*OD*), the file names contain also information of
     20the stream, the field type for forecasts, the method for extracting the vertical wind, and other information such as temporal or horizontal resolution.
    2121
    2222
     
    2424----------------------------------
    2525The 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.
     26The parameters can be listed in any order with one parameter per line.
    2727Comments are started with a '#' - sign. Some of these parameters can be overruled by the command line
    2828parameters given to the :literal:`submit.py` script.
    29 All parameters have default values. Only those parameters which have to be changed
    30 must be listed in the :literal:`CONTROL` files.
     29All parameters have default values; only those parameters which deviate from default
     30have be listed in the :literal:`CONTROL` files.
    3131
    3232
     
    3535
    3636A 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 adaptations and understand what's possible to
    38 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.
     37They can be used as a template for adaptation, and to understand what can be
     38retrievee from ECMWF's archives.
     39There 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.
    4040
    4141
     
    4545------------
    4646The 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
     47in grouped sections together with their default values.
     48In :doc:`control_params`, you can find a more
     49detailed description with additional hints, possible values, and further information about
    4950the setting of these parameters.
    5051
Note: See TracChangeset for help on using the changeset viewer.
hosted by ZAMG