Changeset d720895 in flex_extract.git for Documentation/html/_sources/installation.rst.txt
- Timestamp:
- Dec 19, 2019, 8:12:11 PM (4 years ago)
- Branches:
- master, ctbto, dev
- Children:
- e70c85f
- Parents:
- 76c37a9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
Documentation/html/_sources/installation.rst.txt
r30f7911 rd720895 132 132 .. _ref-requirements: 133 133 134 Environment requirements135 ============ ============134 Dependencies 135 ============ 136 136 137 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. 138 139 138 140 139 Generally speaking, ``flex_extract`` requires `Python 3`_ and Fortran together with certain modules / libraries. 141 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: 143 144 .. code-block:: sh 145 146 $ dpkg -s libeccodes-dev | grep Status 147 # or 148 $ rpm -q libeccodes-dev 142 149 143 150 … … 198 205 ================================================= 199 206 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. 207 Some 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. 203 208 204 209 … … 218 223 -------------------- 219 224 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. 225 To check whether the Fortran program ``CONVERT2`` has been compiled and runs properly, it can be applied to a prepared minimal dataset. 226 227 For this, go from the ``flex_extract`` root directory to the ``Testing/Installation/Convert/`` directory and execute the Fortran program. 225 228 226 229 .. note:: … … 229 232 .. code-block:: bash 230 233 231 cd test/Installation/Convert232 # callthe Fortran progam without arguments233 ../../../ source/fortran/CONVERT2234 235 The installation was successfull if it showed the followingoutput:234 cd Testing/Installation/Convert 235 # execute the Fortran progam without arguments 236 ../../../Source/Fortran/CONVERT2 237 238 The installation was successfull if you obtain on standard output: 236 239 237 240 .. code-block:: bash
Note: See TracChangeset
for help on using the changeset viewer.