1. General Batch Policies
2. Contributed Equipment Policies

Arches

• Jobs are limited by wallclock time as follows:
  • delicatearch: 72 hours
  • marchingmen: 72 hours
  • tunnelarch: 5 days, 120 hours
  • sanddunearch: 72 hours
• Any individual may have up to half of the available nodes busy for the time equal the wallclock limit (one job of "n" nodes, or several jobs adding up to "n" nodes, where "n" is half of the available batch nodes).
• Any process not running under batch control will be killed after 15 minutes cpu time. On the cluster it is best to run all tests through batch control. Issuing the command "qsub -I" will usually return an interactive prompt on a batch node. If no nodes are available this way, only then should tests be run on the interactive node.
• User's who have exhausted their allocation will not have their jobs dispatched unless there are free cycles on the system available.

If you have a critical need to circumvent these policies, please send a detailed explaination to Julio Facelli, the Director of CHPC, facelli@chpc.utah.edu explaining your special requirements (why your job cannot be checkpointed etc.)

Updraft

• Preemption: On Updraft we have introduced the notion of preemption. This means that jobs that have preemptor status will "override" jobs which are running with preemptee status. You will always run with preemptee status if you do not have, or are out of allocation. In addition, you may choose to run with preemptee status if you have allocation. Your jobs will then be charged at .25 the regular rate. To select this, you need to add qos=preemptable to your -l PBS flag. So you would add something like
  #PBS nodes=4:ppn=32,walltime=10:00:00,qos=preemptable to your PBS script.

• Reservations

Reservation	Node/core count	QOS entry point(s)
Test	2/16 (1%)	test and big_run
Uintah	169/1352 (66%)	uintah,big_run,preemptable and freecycle
General	85/680 (33%)	general,big_run,preemptable and freecycle

• Qualities of Service (qos)

QOS	Relative Priorities	Properties
bigrun	+++	approval required allocation required preemptor MAX runtime 72 hours
uintah	++	approval required allocation required preemptor MAX runtime 12 hours
test	++	allocation required must request qos=test MAX runtime 2 hours
general	++	allocation required preemptor MAX runtime 24 hours
preemptable	+	allocation required but charged at .25 normal rate preemptee MAX runtime 24 hours
freecycle	zero	out of, or no allocation preemptee MAX runtime 24 hours

• Dedicated Access Times (DATs): There will be 3 times each month where DATs (Dedicated Access times) are reserved. You may sign up for the general DAT by sending a request to issues@chpc.utah.edu. The DATs for the uintah users are on the 1st and 3rd weeks of the month. The general DATs are on the 4th week of the month. The DATs give you access to the entire system, and run (24 hours) from Monday at Noon until Wednesday at Noon.

Please see the Adding Nodes Policy Page.