experimental_workflow
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
experimental_workflow [2015/02/26 15:11] – lcardoso | experimental_workflow [2015/09/16 10:39] – [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 |
+ | * [[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, 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.txt · Last modified: 2015/09/16 10:39 by trisset