Changes between Version 19 and Version 20 of cypress/using

Timestamp:

04/27/15 15:41:17 (10 years ago)

Author:

fuji

Comment:

Add Idev

cypress/using

@@ -149 +149 @@
 In the script above we request 20 cores on one node of Cypress (which is all the cores available on any node). As SLURM regards tasks as being analogous to MPI processes, it’s better to use the cpus-per-task directive when employing OpenMP parallelism. Additionally, the SLURM export variable $SLURM_JOB_CPUS_PER_NODE stores whatever value we assign to cpus-per-task, and is therefore our candidate for passing to OMP_NUM_THREADS.
 
-
+== Submitting an interactive job ==
+
+For those who develop their own codes, we provide the app, `idev` to make interactive access to a set of compute nodes, in order to quickly compile, run and validate MPI or other applications multiple times in rapid succession.
+
+==== The app `idev`, (Interactive DEVelopment) ====
+
+The `idev` application creates an interactive development environment from the user's login window. In the `idev` window the user is connected directly to a compute node from which the user can launch executables directly. 
+The `idev` command submits a batch job that creates a copy of the batch environment and then goes to sleep. After the job begins, `idev` acquires a copy of the batch environment, SSH's to the master node, and then re-creates the batch environment.
+
+==== How to use `idev` ====
+
+On Cypress login nodes (cypress1 or cypress2), 
+{{{#!bash
+[user@cypress1 ~]$ idev
+}}}
+
+In default, `idev` submit a job requesting '''one node for one hour'''. It also requests two ''Intel Phi'' (MIC) co-processors. 
+If there is an available node,  your job will become active immediately and `idev` app initiates a ssh session to the computing node. For example:
+
+{{{#!bash
+[fuji@cypress1 ~]$ idev
+Requesting 1 node(s)  task(s) to normal queue of defq partition
+1 task(s)/node, 20 cpu(s)/task, 2 MIC device(s)/node
+Time: 0 (hr) 60 (min).
+Submitted batch job 8981
+JOBID=8981 begin on cypress01-100
+--> Creating interactive terminal session (login) on node cypress01-100.
+--> You have 0 (hr) 60 (min).
+Last login: Mon Apr 27 14:45:38 2015 from cypress1.cm.cluster
+[fuji@cypress01-100 ~]$
+}}}
+
+Note the prompt, "cypress01-100", in the above session. It is your interactive compute-node prompt. You can load modules, compile codes and test codes.
+`idev` transfers the environmental variables to computing node. Therefore, if you have loaded some module on the login node, you don't have to load the same module again.
+
+==== Options ====
+
+By default only a single node is requested for 60 minutes. However, you can change the limits with command line options, using syntax similar to the request specifications used in a job script. 
+The syntax is conveniently described in the `idev` help display:
+
+{{{#!bash
+[fuji@cypress1 ~]$ idev --help
+-c|--cpus-per-task=     : Cpus per Task
+-N|--nodes=             : Number of Nodes
+-n|--ntasks-per-node=   : Number of Tasks per Node
+--gres=                 : Number of MIC per Node
+-t|--time=              : Wall Time
+}}}
+
+For example, if you want to use 4 nodes for 4 hours,
+
+{{{#!bash
+[fuji@cypress1 ~]$ idev -N 4 -t 4:00:00
+Requesting 4 node(s)  task(s) to normal queue of defq partition
+1 task(s)/node, 20 cpu(s)/task, 2 MIC device(s)/node
+Time: 04 (hr) 00 (min).
+Submitted batch job 8983
+JOBID=8983 begin on cypress01-100
+--> Creating interactive terminal session (login) on node cypress01-100.
+--> You have 04 (hr) 00 (min).
+Last login: Mon Apr 27 14:48:45 2015 from cypress1.cm.cluster
+[fuji@cypress01-100 ~]$
+}}}
+
+==== Questions or Suggestions ====
+
+If you have ideas for enhancing `idev` with new features or any questions, please send email to hpcadmin@tulane.edu.