NQS: Network Queueing System

Super-K users: NQS only accepts submissions on sukap001-009. It runs on sukap010.

First: make sure that all your path names are written out in any code that you submit.
If you are running a binary executable that reads locally stored files, then you will need to write a little shell script to avoid issues with path definitions:

#! /bin/csh -f

set dir=/home/ethrane/nuance/data
cd $dir
./nuanceMc.exe ./eric_evts.cards

Make sure your shell script doesn't contain any commands like "echo" that require output to screen or nqs may decide it can't run the script.

to submit: qsub -eo -o log script.csh
to monitor: qstat @sukap010
to delete: qdel -K -r sukap010 -u ethrane 119326
if qdel fails to kill a job: wait 30 minutes and check again. If it still hasn't been killed, you may need to contact your system administrator.

some submissions work only if you have to add "-q atmpd" to the qsub command, (e.g., skdetsim). The -q flag sets the queue. The atmpd queue is supposed to have no time limit.

To take advantage of the full parallel processing capabilities of NQS: it can be useful to break the job into many separate submissions like so: sk2mc.csh.

Large error and log files are sometimes created during large batch jobs. If you don't remove them, they can quickly reach GB in size and fill up your entire home directory space.

NQS Utilities

qlist.csh: streamlined version of qstat
qkill.csh: kill all NQS jobs at once
qlist.sed: .sed script necessary for both
qclean.pl removes .log and .err files every 10 seconds for up to three hours or until NQS is idle.

Back to Resources