Jobs are submitted with the
The options tell Torque information about the job, such as what resources will be needed. These can be specified in the job-script as PBS directives, or on the command line as options, or both (in which case the command line options take precedence should the two contradict each other). For each option there is a corresponding PBS directive with the syntax:
For example, you can specify that a job needs 2 nodes and 8 cores on each node by adding to the script the directive:
or as a command-line option to
qsub when you submit the job:
PBS directives and qsub options for working interactively
Options for running interactively on the compute nodes:
Don't just submit the job, but also wait for it to start and connect
stdinto the current terminal.
Enable X forwarding, so programs using a GUI can be used during the session (provided you have X forwarding to your workstation set up)
Run specifically in the interactive queue. At NYU HPC, this queue has smaller job limits (maximum of two nodes and 4 hours walltime) but very high priority.
Pass the current environment to the interactive batch job
- To leave an interactive batch session, type
exitat the command prompt.
Certain tasks need user interaction - such as debugging and some GUI-based applications. However the HPC clusters rely on batch job scheduling to efficiently allocate resources. Interactive batch jobs allow these apparently conflicting requirements to be met.
When you start an interactive batch job the command prompt is not immediately returned. Instead, you wait until the resource is available when the prompt is returned and you are on a compute node and in a batch job - much like the process of logging in to a host with
ssh. To end the session, type '
exit', again just like the process of logging in and out with
To use any GUI-based program within the interactive batch session you will need to extend X forwarding with the
-X option or directive. This of course still relies on you having X forwarding at your login session - try running '
xterm' before starting the interactive to verify that this is working correctly.
You can request resources for an interactive batch session just as you would for any other job, for example to request 4 processors with 4GB memory for 2 hours:
By default your job will be placed in the s48 queue for serial jobs. For higher priority (thus less time waiting in the queue for the session to start) or to access more than one node, submit the job to the interactive queue with
Your interactive session will start in your home directory, you can jump to the directory you submitted from with: