Auger Command Files

Fri, 10/04/2013 - 09:46 — chen

To submit a job to the farm you need to create a configuration script that describes your job(s). There are two different formats that this configuration file can be in. The first is a flat file format which has been supported for years. The second format is an XML based format, which allows some additional description.

Batch Job Tracks

Thu, 10/03/2013 - 11:10 — ychen

NOTE: This information is no longer valid for our slurm-based queue manager. See 'account' and 'partition' information under https://scicomp.jlab.org/cli/add-job.html

All jobs submitted to the farm will belong to a track. The track is used to determine both what queue a job runs in and what type of job it is for accounting purposes.

Text Command File

Wed, 10/02/2013 - 14:36 — ychen

Keywords

Auger Examples

Wed, 10/02/2013 - 14:30 — ychen

This page gives examples of different types of configuration scripts for Auger. This document assumes that you are familiar with the syntax of these scripts and therefore doesn't spend much time explaining them. These files are intended to be used as templates for you to write your own configuration files, changing the values (files, names, commands, emails), to suit your needs. For a detailed description of these configuration files see the Auger Command Files.

farmhosts

Wed, 10/02/2013 - 14:25 — ychen

Name
    farmhosts - displays hosts and their static and dynamic resources
Syntax
    farmhosts
Description
    Displays information about hosts. It also lists all the job id which
running on that node. The state of farm node is displayed in 5 bits,
FJDOB.

           1st bit is F if the node is free for more job, otherwise is "-"

           2nd bit is J if the maximum jobs are running on the node, otherwise is "-"

jkill

Wed, 10/02/2013 - 14:06 — ychen

Name
    jkill - Kill queued and executing Auger jobs
Syntax
   jikll job-id1 job-id2 [.... job-idn]    
        or    
   jkill 0
Description
jkill will delete the requested job id from the batch queue.
Only those jobs which the user has permission to modify will be
affected. In the first form, the command will delete a batch job and
its associated jcache requests. In the second form, a special job id of

jsub

Wed, 10/02/2013 - 13:45 — ychen

Name

    jsub - Submit an Auger job to farm batch system.

Syntax  

jobstat

Wed, 10/02/2013 - 12:46 — ychen

Name
   jobstat - batch job status query
Syntax  
   jobstat [-h] [-u username] [-j job_id] [-s stat ] [-a account] [-q queue]
Description
  Display status pbs batch jobs and other information about the selected batch jobs. By default, jobstat show all jobs if no jobId is given. Use [ -u username ] option to select the jobs for specified users.Jobstat will display the job status and related information, such as,
Exec_HOST, SUBMIT_TIME, CPUTIME, WALLTIME and ACCOUNT etc. The status

FAQ

Wed, 10/02/2013 - 11:49 — ychen

How does Auger handle different types of input file?

There are two different ways that a file is staged to a farm node. 

Fairshare

Wed, 10/02/2013 - 11:38 — ychen

The batch farm uses a fair share system to schedule jobs using Slurm, the batch scheduler and the fair tree algorithm.  Fair share guarantees that CPU allocations are balanced out according to an allocation over time.

To use a project, the user specified the name of the project using the PROJECT parameter, and Auger will then schedule the work to be done using that project account/user (if the user is a member of that project).

Pages

Powered by Drupal