exp_create_task
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| exp_create_task [2014/06/17 17:15] – bguillon | exp_create_task [2017/08/22 14:32] (current) – migrate from scenario.desc to scenario.yaml mimbert | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Create an experiment ===== | ===== Create an experiment ===== | ||
| - | Now that all the experiment material has been successfully uploaded on the airlock you will have to create a task file. The task file is a simple tar.gz archive file that contains your experiment material alongside an experiment description file: `scenario.desc`. | + | Now that all the experiment material has been successfully uploaded on the airlock you will have to create a task file. The task file is a simple tar.gz archive file that contains your experiment material alongside an experiment description file: `scenario.yaml`. |
| ==== The experiment description file ==== | ==== The experiment description file ==== | ||
| - | The experiment description file called `scenario.desc` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment. | + | The experiment description file called `scenario.yaml` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment. |
| Here is a simple example of a `scenario.desc` file: | Here is a simple example of a `scenario.desc` file: | ||
| Line 16: | Line 16: | ||
| # Scenario textual description | # Scenario textual description | ||
| # | # | ||
| - | desc OFDM tx-rx example scenario for CorteXlab | + | description: |
| # Experiment maximum duration | # Experiment maximum duration | ||
| # Time after which the experiment is forced to stop | # Time after which the experiment is forced to stop | ||
| - | # | + | # |
| - | durat 2 | + | duration: 120 |
| # Node list | # Node list | ||
| Line 27: | Line 27: | ||
| # | # | ||
| # | # | ||
| - | # | + | # nodes: |
| - | # entry (entry point script relative to the task root) | + | # (machine): |
| - | # exit (exit point script relative to the task root. Use " | + | # command: |
| - | node4: | + | nodes: |
| - | entry benchmark_rx.py | + | |
| - | | + | |
| - | exit none | + | node6: |
| - | + | | |
| - | node6: | + | |
| - | entry benchmark_tx.py | + | |
| - | | + | |
| - | exit none | + | |
| </ | </ | ||
| Line 46: | Line 42: | ||
| ==== Creating the task file ==== | ==== Creating the task file ==== | ||
| - | Once the `scenario.desc` file is written, put all the experiment material and the `scenario.desc` file in the same directory. The file tree could look like something like that: | + | Once the `scenario.yaml` file is written, put all the experiment material and the `scenario.yaml` file in the same directory. The file tree could look like something like that: |
| < | < | ||
| ... | ... | ||
| Line 53: | Line 49: | ||
| │ ├── benchmark_tx.py | │ ├── benchmark_tx.py | ||
| │ ├── receive_path.py | │ ├── receive_path.py | ||
| - | │ ├── scenario.desc | + | │ ├── scenario.yaml |
| │ ├── transmit_path.py | │ ├── transmit_path.py | ||
| │ └── uhd_interface.py | │ └── uhd_interface.py | ||
| Line 67: | Line 63: | ||
| **Note:** You can get help on the Minus CLI at anytime with `minus -h` | **Note:** You can get help on the Minus CLI at anytime with `minus -h` | ||
| + | |||
| + | |||
| + | => [Submitting the task to the experiment scheduler](exp_submit_task) | ||
exp_create_task.1403018144.txt.gz · Last modified: 2014/06/17 17:15 by bguillon