Commit 26109dff authored by Zohreh MOSTAANI's avatar Zohreh MOSTAANI

[cmdline][doc] editer the executors part

parent dbe4ce98
...@@ -66,7 +66,7 @@ a simple environment with PDB support without advanced features ...@@ -66,7 +66,7 @@ a simple environment with PDB support without advanced features
Here, the ``--prefix`` option is used to tell the scripts where all our data Here, the ``--prefix`` option is used to tell the scripts where all our data
formats, toolchains and algorithms are located. This option can be set formats, toolchains and algorithms are located. This option can be set
in your configuration file (see ``beat config``). in your configuration file (see :ref:`beat-cmdline-configuration`).
This command displays for each block the files containing the data to use as This command displays for each block the files containing the data to use as
input, and the files generated by the outputs of the block. input, and the files generated by the outputs of the block.
...@@ -80,10 +80,9 @@ Executors ...@@ -80,10 +80,9 @@ Executors
"Executors" are modules that execute each block in an experiment. On the BEAT "Executors" are modules that execute each block in an experiment. On the BEAT
platform, there is only the one executor, which executes the experiment using platform, there is only the one executor, which executes the experiment using
Docker containers with advanced scheduling and security features. When Docker containers with advanced scheduling and security features. When using ``beat.cmdline`` locally, however, you have the option of using either
developing using ``beat.cmdline``, however, you have the option of using either the BEAT platform's executor, behind the ``--docker`` flag (for more information about using docker executors see :ref:`here <beat-core-local-development>`), or the "local"
the BEAT platform's executor, behind the ``--docker`` flag, or the "local" executor (refer to :ref:`beat-installation` for information about local environment). The local executor, is
executor, provided in this project. The local executor, as explained above, is
much simpler, aimed at providing a smooth development experience. However, much simpler, aimed at providing a smooth development experience. However,
there are two important tradeoffs: there are two important tradeoffs:
...@@ -93,13 +92,6 @@ there are two important tradeoffs: ...@@ -93,13 +92,6 @@ there are two important tradeoffs:
``beat.cmdline`` is used. This means that many BEAT experiments that ``beat.cmdline`` is used. This means that many BEAT experiments that
rely on different/multiple environments will not work. rely on different/multiple environments will not work.
If you want to use the local executor, pay attention to the python environment
used to call `buildout` in your copy of ``beat.cmdline``. The suggested way
to use Bob libraries while developing on the local executor is to use install
``zc.buildout`` in a Python2.7 conda environment with Bob installed. Using
the ``buildout`` command from the environment will make the entire environment
available to ``beat.cmdline`` even when the environment is not active.
.. _beat-cmdline-experiments-displaydata: .. _beat-cmdline-experiments-displaydata:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment