Batch-style processing is available on select nodes of the Unix cluster via Condor.

Condor is a software framework for distributed parallel computation. At Minnesota, we use it both to manage workload on dedicated server clusters, and (in some cases) to farm out work to idle desktop computers

Each Physics linux system is tagged with a “CondorGroup” name corresponding to the research group or entity to which it belongs. It is possible to run jobs on any cluster, but if you are unsure whether you should be using a particular group of machines please check first. <note> You can see which servers belong to each cluster, and what their capabilities are, on the Linux Servers Listing page in MyPhys.

If your research group has no computational resources of its own, there is a general-purpose phys cluster which can be used by anyone. </note>

You can also get an idea of activity within each cluster (although not directly condor-related) at our Ganglia monitoring page

Useful commands for submitting jobs are

• condor_run - for quick & easy job submission
• condor_submit - for full control

Useful commands for job and machine status are

• condor_status shows active machines and queues
• condor_status -submitters shows job submitter summary
• condor_q shows jobs in the local job queue
• condor_q -global shows jobs in the global job queue

You can find some more information at:

• Condor Manual
• Condor Wiki at UW Madison
• Quick Condor Tutorial for Fermilab

Unless you've specifically used condor_compile to build your programs, you'll need to submit your jobs in the “vanilla” universe.

universe = vanilla

Notification = error

Almost all our condor slots are set up as “partitionable”, which means you can request what resources are needed. Try to specify appropriate values in your submit file so that condor can reserve resources for your job (without this, your job will be given default values which may cause it to be held).

• request_cpus (defaults to 1)
• request_memory (defined in megabytes; defaults to the ImageSize or JobVMemory parameters).
• request_disk - (defined in kilobytes; defaults to the DiskUsage parameter. You probably don't need to worry about this one).

By default, the cluster which executes a job is determined by the machine where you issue the condor_submit command - for example, if you submit a job from a CMS system, it will execute on the CMS cluster.

You can override this behavior in your submit file by manipulating the CondorGroup job ClassAd. For example, you could place the following line in your job file to make the jobs run on the CMS server farm:

+CondorGroup = "cmsfarm"

In additionl, you can let your jobs run on any cluster by adding the following line

+CanEvict = True

In this case your job can run on any cluster, but will be pre-empted (ie killed) if a job with a higher rank (based on the group owning the cluster) needs to run.