Differences

This shows you the differences between two versions of the page.

--- experimental_workflow [2015/02/26 14:48] – mimbert
+++ experimental_workflow [2015/02/26 15:11] – lcardoso
@@ Line 5: / Line 5: @@
   - **submit experimental tasks**, with //Minus//
-===== 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, 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 during the requested time.
 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).
@@ Line 18: / Line 18: @@
 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://www.gnu.org/software/screen/) session to avoid loosing jobs in case of network disconnection).
+By default OAR submissions are scheduled as soon as possible. It is also possible to ask for an OAR //reservation// where you choose the date at which the job will be scheduled.
 ===== Submit experimental tasks =====
@@ Line 33: / Line 35: @@
 ===== Interactive or batch experiments =====
+When submitting or reserving an OAR job, you have the choice between interactive or batch:
+  - In //interactive// mode, an interactive subshell is instanciated where you work interactively. The job ends as soon as the interactive shell is closed
+  - In //batch// mode, you pass to command ''oarsub'' the name of an executable file which will be run as soon as the job starts. It is thus possible to write scripts which submit several experimental tasks (for example, to explore the variation of experimental parameters), and to submit OAR jobs which will be run automatically and asynchrously (even during the night).