experimental_workflow
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
experimental_workflow [2015/02/26 14:37] – created mimbert | experimental_workflow [2015/09/16 10:39] (current) – [Book nodes with OAR] trisset | ||
---|---|---|---|
Line 5: | Line 5: | ||
- **submit experimental tasks**, with //Minus// | - **submit experimental tasks**, with //Minus// | ||
- | ===== Book nodes with //OAR// ===== | + | ===== Book nodes with OAR ===== |
- | Only one person can use the whole CorteXlab | + | The booking of the testbed |
+ | This is explained here: | ||
- | The role of //OAR// is to schedule node reservations. It manages | + | * [[Reserve|Book the testbed]] |
- | The principle | + | The state of reservation |
- | A basic example to submit an OAR interactive job requesting all available nodes: | ||
- | |||
- | < | ||
===== Submit experimental tasks ===== | ===== Submit experimental tasks ===== | ||
- | ===== Interactive | + | Once inside a running OAR job, you can submit one or several **Experimental tasks** by using minus: |
+ | < | ||
+ | |||
+ | All submitted minus tasks are enqueued in a simple FIFO and will execute sequentially. | ||
+ | |||
+ | Of course, to be able to schedule experimental tasks, you need to have a running OAR job. | ||
+ | |||
+ | When your OAR job ends, all running and remaining tasks are aborted and removed for the FIFO. | ||
+ | |||
+ | ===== Interactive or batch experiments ===== | ||
+ | When submitting or reserving an OAR job, you have the choice between interactive or batch: | ||
+ | - In // | ||
+ | - In //batch// mode, you pass to command '' |
experimental_workflow.1424957824.txt.gz · Last modified: 2015/02/26 14:37 by mimbert