Changeset a14839a in flex_extract.git for For_developers/Sphinx/source/Support/known_bugs_issues.rst

Timestamp:

May 15, 2020, 2:27:39 PM (4 years ago)

Author:

Petra Seibert <petra.seibert [at) univie.ac.at>

Branches:

master, ctbto, dev

Children:

f20342a

Parents:

b936fd3

Message:

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

File:

• For_developers/Sphinx/source/Support/known_bugs_issues.rst (modified) (3 diffs)

For_developers/Sphinx/source/Support/known_bugs_issues.rst

@@ -15 +15 @@
 ---------------------------------------------------------------------
 
-  See ticket `#263 <https://www.flexpart.eu/ticket/263>`_  on flexpart.eu for information.
+  See ticket `#263 <https://www.flexpart.eu/ticket/263>`_  on flexpart.eu for information. Fixed in v7.1.1.
 
 
@@ -21 +21 @@
 --------------------------------------------------------------
 
-   See ticket `#264 <https://www.flexpart.eu/ticket/264>`_  on flexpart.eu for information.
+   See ticket `#264 <https://www.flexpart.eu/ticket/264>`_  on flexpart.eu for information. Fixed in v7.1.1.
+
 
 ECCODES Error Code 250
 ----------------------
 
-If you get an error message from ECCODES with code 250, locking like this:
+If you get an error message from ECCODES with code 250, looking like this:
 
 .. code-block:: bash
@@ -38 +39 @@
 
 then you have set a wrong maximum level in the :literal:`CONTROL` file! 
-It is important to properly select the maximum level depending on the data set you would like to retrieve. The following model level definitions (number of model levels available) are limited to [16, 19, 31, 40, 50, 60, 62, 91, 137]. The ERA-Interim data set uses 62 model levels and *ERA5* as well as *CERA-20C* uses 137. The operational data set uses different model levels depending on the date. For example, on the 25/06/2013 the operational system started to use 137 model levels. Therefore, everytime you extract data from a date later than 25/06/2013 you have to select LEVEL=137 in the :literal:`CONTROL` file or define a LEVELLIST=1/to/137. Of course you can stop before the top of the atmosphere, such as 60/to/137, but you have to select the maximum level 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 introducstion date. 
+It 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. 
+
+The ERA-Interim data set uses 62 model levels and *ERA5* as well as *CERA-20C* uses 137. 
+
+The 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. 
 
 
 .. note::
  
-        Remember that model level 1 corresponds to the top of the atmosphere and then increases in the direction of the surface.
+        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.