Changeset a9d33f6 in flex_extract.git for For_developers/Sphinx/source/installation.rst


Ignore:
Timestamp:
Jun 1, 2020, 7:58:31 PM (4 years ago)
Author:
Petra Seibert <petra.seibert [at) univie.ac.at>
Branches:
master, ctbto, dev
Children:
5bee29a
Parents:
5920b7f
Message:

changes related to makefile, structure and names of top-level sections

File:
1 edited

Legend:

Unmodified
Added
Removed

  • For_developers/Sphinx/source/installation.rst

    rb936fd3 ra9d33f6  
    135135============
    136136
    137 The software required for running ``flex_extract`` depends on the :doc:`Documentation/Overview/app_modes` and therefore is described in the respective specific installation sections.
     137The software required to run ``flex_extract`` depends on the :doc:`Documentation/Overview/app_modes` and therefore is described in the respective specific installation sections.
    138138   
    139139Generally speaking, ``flex_extract`` requires `Python 3`_ and Fortran together with certain modules / libraries.
    140 We 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 
    142 Before 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:
     140We 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 (Debian-based system) ``dpkg -s <package-name> |  grep Status`` or (Redhat-based system)``rpm -q <package_name>``. For example:
    143143
    144144.. code-block:: sh
    … …  
    150150
    151151
    152 
    153 
    154 
    155152.. _ref-install-fe:
    156153
    … …  
    183180    Installation/local
    184181
    185 
    186 
    187 
    188 
    189 
    190 
    191 
    192 
    193 
    194 
    195 
    196 
    197 
    198 
    199 
    200    
    201    
    202182   
    203183
    … …  
    206186
    207187Some 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.
    208 
    209 
    210 
    211 
    212 
    213 
    214 
    215188
    216189
Note: See TracChangeset for help on using the changeset viewer.
hosted by ZAMG