User Tools

Site Tools


experimental_workflow

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
experimental_workflow [2015/02/26 14:48] mimbertexperimental_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 testbed at the same time. The //OAR// scheduler is used to book nodes on the platformAs soon as you book one or more nodes, the CorteXlab room is reserved for your usage.+The booking of the testbed in order to launch and experiment is done the the OAR tool and the oarsub command. 
 +This is explained here: 
  
-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).+ [[Reserve|Book the testbed]]
  
-The principle of operation of CorteXlab is that users submit jobs to OARWhen the job starts, the user gets exclusive access to the platform, and inside an OAR job, the user can perform (interactively, or in batch) one or several experiments.+The state of reservation of the CorteXlab testbed can be visualized here: http://xp.cortexlab.fr/drawgantt/
  
-A basic example to submit an OAR interactive job requesting all available nodes, for the default duration (which is 2 hours): 
- 
-<code>$ oarsub -I -l nodes=BEST</code> 
- 
-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). 
  
 ===== 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 //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).
experimental_workflow.1424958508.txt.gz · Last modified: 2015/02/26 14:48 by mimbert

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki