experimental_workflow
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
experimental_workflow [2015/02/26 14:48] – 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, for the default duration (which is 2 hours): | ||
- | |||
- | < | ||
- | |||
- | This command will wait for the resources to be available, and as soon as they are, a job is allocated, is started, and a subshell is instanciated where you can work on experiments. As soon as the subshell is closed, the job ends. (It can be usefull to work in a [screen](https:// | ||
===== Submit experimental tasks ===== | ===== Submit experimental tasks ===== | ||
Line 33: | Line 29: | ||
===== Interactive or batch experiments ===== | ===== 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.1424958508.txt.gz · Last modified: 2015/02/26 14:48 by mimbert