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 15:11] – lcardoso | experimental_workflow [2015/09/16 10:39] (current) – [Book nodes with OAR] trisset | ||
---|---|---|---|
Line 7: | Line 7: | ||
===== Book nodes with OAR ===== | ===== Book nodes with OAR ===== | ||
- | To avoid cross interference between multiple experiments, | + | 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:// | ||
- | |||
- | By default OAR submissions are scheduled as soon as possible. It is also possible to ask for an OAR // | ||
===== Submit experimental tasks ===== | ===== Submit experimental tasks ===== |
experimental_workflow.1424959907.txt.gz · Last modified: 2015/02/26 15:11 by lcardoso