experimental_workflow
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| experimental_workflow [2015/02/26 14:57] – mimbert | experimental_workflow [2015/02/26 15:10] – lcardoso | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Book nodes with OAR ===== | ===== Book nodes with OAR ===== | ||
| - | Only one person can use the whole CorteXlab testbed at the same time. The //OAR// scheduler is used to book nodes on the platform. As soon as you book one or more nodes, the CorteXlab room is reserved for your usage. | + | To avoid cross interference between multiple experiments, |
| 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 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). | ||
experimental_workflow.txt · Last modified: 2015/09/16 10:39 by trisset