If the environment field is not given, the system will try to find an appropriate environment using the database name as reference. If no database environment declares support for the database, then the execution will fail.
The content of name and version follows the same pattern as for the execution environment as can be seen on the `beat environments`_ page. The name is what comes before the parenthesis and the version is the content found between the parenthesis.
The "protocols" field is where the datasets for each protocol is defined. In the example above only one protocol is defined. Implementing a new protocol means adding a new entry to the list of protocols. Each protocol has three main component:
* **name:** The name of the protocol which is "idiap" in this case.
...
...
@@ -389,4 +391,26 @@ new evaluation protocols into the platform. Besides, at the experiment level,
this allows to re-use a toolchain on a different database, with almost no
configuration changes from the user.
.. _beat-system-databases-docker:
Databases and Docker
====================
The BEAT docker images can be found on the `beat Docker Hub`_ page.
To get one of the image on your machine, just type the classic Docker command:
$ docker pull beatenv/beat.env.XXX:TAG
Note that there are no "latest" version because of the reproducibility goal of BEAT. Therefore, you will always have to pull the precise version you want to use.
In order to list all the BEAT related Docker images on your machine, use the following command:
$ beat environments list docker
To have a more curated list of images, the following command shows only the database related BEAT images:
