source: flex_extract.git/Documentation/html/_sources/Support/known_bugs_issues.rst.txt @ 08c9091

ctbtodev
Last change on this file since 08c9091 was 08c9091, checked in by Anne Philipp <anne.philipp@…>, 4 years ago

updated online docu (rm tabs)

  • Property mode set to 100644
File size: 2.4 KB
Line 
1Known Bugs and Issues
2*********************
3
4Release v7.1
5============
6
7
8CDS API and ERA5 data
9---------------------
10
11  See ticket `#230 <https://www.flexpart.eu/ticket/230>`_  on flexpart.eu for information.
12
13
14Installation problems with ``GATEWAY`` and ``DESTINATION`` parameters
15---------------------------------------------------------------------
16
17  See ticket `#263 <https://www.flexpart.eu/ticket/263>`_  on flexpart.eu for information. Fixed in v7.1.1.
18
19
20Installation problems with the Fortran program ``calc_etadot``
21--------------------------------------------------------------
22
23   See ticket `#264 <https://www.flexpart.eu/ticket/264>`_  on flexpart.eu for information. Fixed in v7.1.1.
24
25
26ECCODES Error Code 250
27----------------------
28
29If you get an error message from ECCODES with code 250, looking like this:
30
31.. code-block:: bash
32
33    ECCODES ERROR   :   wrong size (184) for pv it contains 276 values
34    ECCODES ERROR   :  get: pv Passed array is too small
35    ... ERROR CODE: 250
36    ... ERROR MESSAGE:
37          Command '['<path-to-flex_extract>/flex_extract_v7.1/Source/Fortran/calc_etadot']' returned non-zero exit status 250.
38    ... FORTRAN PROGRAM FAILED!
39
40then you have set a wrong maximum level in the :literal:`CONTROL` file!
41It is important to properly select the maximum level depending on the data set you would like to retrieve. Only the following values of the number of model levels available are valid: 16, 19, 31, 40, 50, 60, 62, 91, 137.
42
43The ERA-Interim data set uses 62 model levels and *ERA5* as well as *CERA-20C* uses 137.
44
45The operational data sets use different numbers, depending on the date. For example, from 25/06/2013 on, 137 model levels were used in the operational system. Therefore, every time you extract data from a date later than 25/06/2013 you have to select LEVEL=137 in the :literal:`CONTROL` file, or you have to define LEVELLIST=1/to/137. Of course, you can stop before the top of the atmosphere, such as 60/to/137, but you have to include the maximum level number (i. e., the lowest level, see note below!) number as the last one. Table 2 in the `scientific model description paper <https://www.geosci-model-dev-discuss.net/gmd-2019-358/>`_ gives an overview of the level lists and the corresponding date they were introduced.
46
47
48.. note::
49 
50     Be aware that the ECMWF model counts the levels from the top of the atmosphere downward to the surface. Level 1 is the topmost level, and e.g. 137 would be the level closest to the ground.
Note: See TracBrowser for help on using the repository browser.
hosted by ZAMG