experimental_workflow
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
experimental_workflow [2015/02/26 14:37] – created mimbert | experimental_workflow [2015/09/16 10:39] – [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 |
+ | * [[Reserve|Book | ||
- | The role of //OAR// is to schedule node reservations. It manages **jobs** associated with users, which has a start time, a duration (walltime), and uses some resources (CorteXlab nodes). | + | The state of reservation of the CorteXlab testbed can be visualized here: http://xp.cortexlab.fr/ |
- | The principle of operation of CorteXlab is that users submit jobs to OAR. When the job starts, the user gets exclusive access to the platform, and inside an OAR job, the user can perform (interactively, | ||
- | A basic example to submit an OAR interactive job requesting all available nodes: | + | ===== Submit experimental tasks ===== |
- | < | + | Once inside a running OAR job, you can submit one or several **Experimental tasks** by using minus: |
- | ===== Submit experimental tasks ===== | + | < |
- | ===== Interactive or batch experiments ===== | + | 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.txt · Last modified: 2015/09/16 10:39 by trisset