ctbtodev
Last change
on this file since 41c9dbc was
41c9dbc,
checked in by Anne Philipp <anne.philipp@…>, 5 years ago
|
Large update of Sphinx doc; moved Sphinx source to dev dir; Cleaned control files
|
-
Property mode set to
100644
|
File size:
2.7 KB
|
Rev | Line | |
---|
[41c9dbc] | 1 | ***************** |
---|
| 2 | Application Modes |
---|
| 3 | ***************** |
---|
| 4 | |
---|
| 5 | .. role:: underline |
---|
| 6 | :class: underline |
---|
| 7 | |
---|
| 8 | .. _member state: https://www.ecmwf.int/en/about/who-we-are/member-states |
---|
| 9 | .. _instructions: https://apps.ecmwf.int/registration/ |
---|
| 10 | |
---|
| 11 | |
---|
| 12 | .. _ref-app-modes: |
---|
| 13 | |
---|
| 14 | Arising from the two user groups described in :doc:`../../Ecmwf/access`, ``flex_extract`` has 4 different :underline:`user application modes`: |
---|
| 15 | |
---|
| 16 | .. _ref-remote-des: |
---|
| 17 | |
---|
| 18 | 1. Remote (member) |
---|
| 19 | In the **Remote mode** the user works directly on ECMWF Linux member state server, such as ``ecgate`` or ``cca``. The software will be installed in the ``$HOME`` directory. The user does not need to install any of the additional third-party libraries mentioned in :ref:`ref-requirements` as ECMWF provides everything with environment modules. The module selection will be done automatically in ``flex_extract``. |
---|
| 20 | |
---|
| 21 | .. _gateway: |
---|
| 22 | |
---|
| 23 | 2. Gateway (member) |
---|
| 24 | The **Gateway mode** can be used if a local member state gateway server is in place. Then the job scripts can be submitted to the ECMWF Linux member state server via the ECMWF web access tool ``ecaccess``. The installation script of ``flex_extract`` must be executed at the local gateway server such that the software will be installed in the ``$HOME`` directory at the ECMWF server and some extra setup is done in the local ``flex_extract`` directory at the local gateway server. For more information about establishing a gateway server please see section ???. For the **Gateway mode** the necessary environment has to be established which is described in :ref:`ref-local-prep`. |
---|
| 25 | |
---|
| 26 | .. _local: |
---|
| 27 | |
---|
| 28 | 3. Local member |
---|
| 29 | Scripts are installed and executed on a local machine, either in the current ``flex_extract`` directory or in a path given to the installation script. Under this scenario a software environment similar to that at ECMWF is required. Additionally, Web API's have to be installed to access ECMWF server. The complete installation process is described in :ref:`ref-local-prep`. |
---|
| 30 | |
---|
| 31 | 4. Local public |
---|
| 32 | Scripts are installed and executed on a local machine, either in the current ``flex_extract`` directory or in a path given to the installation script. Under this scenario a software environment similar to that at ECMWF is required. Additionally, Web API's have to be installed to access ECMWF server. The complete installation process is described in :ref:`ref-local-prep`. In this case a direct registration at ECMWF is necessary and the user has to accept a specific license agreement for each dataset he/she intends to retrieve. |
---|
| 33 | |
---|
| 34 | |
---|
| 35 | An overview is sketched in figure :ref:`ref-fig-marsaccess`. |
---|
| 36 | |
---|
| 37 | .. _ref-fig-marsaccess: |
---|
| 38 | |
---|
| 39 | .. figure:: ../../_static/Diagramm_MarsAccess2.png |
---|
| 40 | |
---|
| 41 | Application modes |
---|
| 42 | |
---|
| 43 | |
---|
| 44 | |
---|
| 45 | .. toctree:: |
---|
| 46 | :hidden: |
---|
| 47 | :maxdepth: 2 |
---|
Note: See
TracBrowser
for help on using the repository browser.