Changeset d720895 in flex_extract.git for Documentation/html/_sources/installation.rst.txt


Ignore:
Timestamp:
Dec 19, 2019, 8:12:11 PM (4 years ago)
Author:
Anne Philipp <anne.philipp@…>
Branches:
master, ctbto, dev
Children:
e70c85f
Parents:
76c37a9
Message:

updated online docu

File:
1 edited

Legend:

Unmodified
Added
Removed
  • Documentation/html/_sources/installation.rst.txt

    r30f7911 rd720895  
    132132.. _ref-requirements:
    133133 
    134 Environment requirements
    135 ========================
     134Dependencies
     135============
    136136
    137137The software required for running ``flex_extract`` depends on the :doc:`Documentation/Overview/app_modes` and therefore is described in the respective specific installation sections.
    138 
    139138   
    140139Generally speaking, ``flex_extract`` requires `Python 3`_ and Fortran together with certain modules / libraries.
    141140We tested ``flex_extract`` with the python3 package from the the GNU/Linux distribution and Anaconda Python. The required python3 modules should prefarably be installed as distribution packages, or alternatively using Python's own package manager ``pip`` (this may mess up some aspects of your python installation, especially if you use ``pip`` as root. Think about using virtual environments.).
     141
     142Before installing the system packages check the availability with ``dpkg -s <package-name> |  grep Status`` or ``rpm -q <package_name>``, depending on your system. For example:
     143
     144.. code-block:: sh
     145
     146   $ dpkg -s libeccodes-dev |  grep Status
     147   # or
     148   $ rpm -q libeccodes-dev
    142149
    143150
     
    198205=================================================
    199206
    200 Some users might like to incorporate ``flex_extract`` directly into the ``FLEXPART``
    201 distribution. Then the installation path has to be changed by setting the parameter
    202 `installdir` in the ``setup.sh`` file to the ``script`` directory in the ``FLEXPART`` root directoy.
     207Some users might wish to incorporate ``flex_extract`` directly into the ``FLEXPART`` distribution. Then the installation path has to be changed by setting the parameter `installdir` in the ``setup.sh`` file to the ``script`` directory in the ``FLEXPART`` root directoy.
    203208
    204209
     
    218223--------------------
    219224
    220 To check if the compilation of the Fortran program ``CONVERT2`` was successful
    221 a quick program call on a minimal prepared dataset can be done.
    222 
    223 For this, go from the ``flex_extract`` root directory to the test
    224 directory and call the executable of the Fortran program.
     225To check whether the Fortran program ``CONVERT2`` has been compiled and runs properly, it can be applied to a prepared minimal dataset.
     226
     227For this, go from the ``flex_extract`` root directory to the ``Testing/Installation/Convert/`` directory and execute the Fortran program.
    225228
    226229.. note::
     
    229232.. code-block:: bash
    230233   
    231    cd test/Installation/Convert
    232    # call the Fortran progam without arguments
    233    ../../../source/fortran/CONVERT2
    234 
    235 The installation was successfull if it showed the following output:
     234   cd Testing/Installation/Convert
     235   # execute the Fortran progam without arguments
     236   ../../../Source/Fortran/CONVERT2
     237
     238The installation was successfull if you obtain on standard output:
    236239
    237240.. code-block:: bash
Note: See TracChangeset for help on using the changeset viewer.
hosted by ZAMG