Changeset 6931f61 in flex_extract.git for Documentation/html/_sources/quick_start.rst.txt
- Timestamp:
- Jul 8, 2020, 10:00:37 PM (4 years ago)
- Branches:
- master, ctbto, dev
- Children:
- e0005c9
- Parents:
- 8a53342
- File:
-
- 1 edited
-
Documentation/html/_sources/quick_start.rst.txt (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
Documentation/html/_sources/quick_start.rst.txt
r5bee29a r6931f61 65 65 66 66 # On ECMWF server 67 [<ecuid>@ecgb11 ~]$ module load python368 67 [<ecuid>@ecgb11 ~]$ cd flex_extract_vX.X/Run 69 68 … … 104 103 OUTPUTDIR=None 105 104 PP_ID=None 106 JOB_TEMPLATE='job .temp'105 JOB_TEMPLATE='jobscript.template' 107 106 CONTROLFILE='CONTROL_CERA' 108 107 DEBUG=0 … … 138 137 ls -rthl 139 138 140 The last command lists the most recent logs and temporary retrieval directories (usually `` pythonXXXXX``, where XXXXX is the process id). Under ``pythonXXXXX`` a copy of the ``CONTROL`` file is stored under the name ``CONTROL``, the protocol is stored in the file ``prot`` and the temporary files as well as the resulting files are stored in a directory ``work``. The original name of the ``CONTROL`` file is stored in this new file under parameter ``controlfile``.139 The last command lists the most recent logs and temporary retrieval directories (usually ``extractXXXXX``, where XXXXX is the process id). Under ``extractXXXXX`` a copy of the ``CONTROL`` file is stored under the name ``CONTROL``, the protocol is stored in the file ``prot`` and the temporary files as well as the resulting files are stored in a directory ``work``. The original name of the ``CONTROL`` file is stored in this new file under parameter ``controlfile``. 141 140 142 141 .. code-block:: bash 143 142 :caption: "Example structure of ``flex_extract`` output directory on ECMWF servers." 144 143 145 pythonXXXXX144 extractXXXXX 146 145 ├── CONTROL 147 146 ├── prot … … 358 357 359 358 360 Pureforecast361 It is possible to retrieve pureforecasts exceeding one day. The forecast period available depends on the date and forecast field type. Please use MARS catalogue to check the availability. Below are some examples for 36 hour forecasts of *Forecast (FC)*, *Control forecast (CF)* and *Calibration/Validation forecast (CV)*.359 Long forecast 360 It is possible to retrieve long forecasts exceeding one day. The forecast period available depends on the date and forecast field type. Please use MARS catalogue to check the availability. Below are some examples for 36 hour forecasts of *Forecast (FC)*, *Control forecast (CF)* and *Calibration/Validation forecast (CV)*. 362 361 The *CV* field type was only available 3-hourly from 2006 up to 2016. It is recommended to use the *CF* type since this is available from 1992 (3-hourly) on up to today (1-hourly). *CV* and *CF* field types belong to the *Ensemble prediction system (ENFO)* which currently works with 50 ensemble members. 363 362 Please be aware that in this case it is necessary to set the type for flux fields explicitly, otherwise a default value might be selected, different from what you expect! … … 418 417 The forecast field types (e.g. FC, CF, CV, PF) need to declare a combination of (forescast start) time and the (forecast) step. Together they define the actual time. It is important to know the forecast starting times for the dataset to be retrieved, since they are different. In general, it is sufficient to give information for the exact time steps, but it is also possible to have more time step combinations of ``TYPE``, ``TIME`` and ``STEP`` because the temporal (hourly) resolution with the ``DTIME`` parameter will select the correct combinations. 419 418 420 .. todo::421 422 #PS needs to be rephrased423 424 419 .. code-block:: bash 425 420 :caption: Example of a setting for the field types and temporal resolution. It will retrieve 3-hourly fields, with analyses at 00 and 12 UTC and the corresponding forecasts inbetween. … … 451 446 After selecting grid, the ``domain`` has to be defined. The extension in longitude or latitude direction must be an integer multiple of ``grid``. 452 447 453 .. todo::454 455 #PS shouldn't we explain how to define a domain??456 448 457 449 The horizontal resolution for spectral fields is set by the parameter ``RESOL``. For information about how to select an appropriate value please read the explanation of the MARS keyword RESOL as found `in this entry of the ECMWF on-line documentation <https://confluence.ecmwf.int/display/UDOC/Post-processing+keywords#Post-processingkeywords-resol>`_ and `this table (also ECMWF documentation) <https://confluence.ecmwf.int/display/UDOC/Retrieve#Retrieve-Truncationbeforeinterpolation>`_. … … 470 462 471 463 Flux data 472 Flux fields are always forecast fields and contain values of the fluxes accumulated since the start of the respective forecast. As certain re-analysis dataset cover all time steps with analysis fields, it was necessary to define a new parameter set for the definition of the flux fields. The following parameters are used specifically for flux fields, if provided. ``ACCTYPE`` is the field type (must be a type of forecast), ``ACCTIME`` the forecast starting time, and ``ACCMAXSTEP`` the maximum forecast step;``DTIME`` the temporal resolution. ACCTYPE is assumed to be the same during the whole period given by ACCTIME and ACCMAXSTEP. 473 474 .. todo:: 475 476 #PS for which application would this be typical? 477 464 Flux fields are always forecast fields and contain values of the fluxes accumulated since the start of the respective forecast. As certain re-analysis dataset cover all time steps with analysis fields, it was necessary to define a new parameter set for the definition of the flux fields. The following parameters are used specifically for flux fields. ``ACCTYPE`` is the field type (must be a type of forecast), ``ACCTIME`` the forecast starting time, and ``ACCMAXSTEP`` the maximum forecast step;``DTIME`` the temporal resolution. ACCTYPE is assumed to be the same during the whole period given by ACCTIME and ACCMAXSTEP. These values will be set automatically if not provided in a ``CONTROL`` file. 465 478 466 .. code-block:: bash 479 467 :caption: Example setting for the definition of flux fields.
Note: See TracChangeset
for help on using the changeset viewer.
