Mass Storage System

Tue, 10/22/2013 - 10:42 — larrieu

Running multi-threaded code

Fri, 10/04/2013 - 14:51 — chen

Here are examples of how to specify number of CPU for the job.


  • Submitting a one CPU Job

This is how you can request one CPU to run the job. Or use the default value of one (when no CPU tag is specified).

Specifying Output Files

Fri, 10/04/2013 - 14:48 — chen

Here are examples of how to get output files from your farm jobs.


  • Output File

This will copy an output file from the farm node after your job has finished. 

PROJECT: MyProject
TRACK: MyTrack
JOBNAME: MyJob
COMMAND: ls -alF > file.out
OUTPUT_DATA: file.out
OUTPUT_TEMPLATE: /home/user/outdir/file.out

The XML version of this script looks like:

Specifying Input Files

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

Here are examples of how to get input files to your farm jobs.


  • Analyzing One File

This will copy an individual file to the farm node for analysis. 

PROJECT: MyProject
TRACK: MyTrack
JOBNAME: MyJob
COMMAND: ls -alF
INPUT_FILES: /home/user/file.dat

The XML version of this script looks like:

Email Options

Fri, 10/04/2013 - 14:39 — chen

Here are examples of how to control email.


  • Use Different Email Address

This is how you can tell the farm to use a different email address than the user account that submitted the job. 

PROJECT: MyProject
TRACK: MyTrack
JOBNAME: MyJob
COMMAND: ls -alF
MAIL: otherUser@jlab.org

The XML version of this script looks like (email at job level is turned off, even with job="true'):

Specify Constraints and Resources

Fri, 10/04/2013 - 14:37 — chen

Here are examples of specifying constraints or requesting resources for your job.


  • Specifying a Time Limit

This is an example of constraining the amount of time a job can use.
The units are minutes. So, 60 is 60 minutes or one hour. This is the
"walltime" of the job or the amount of time that the job will be
running before the batch system stops the job.

Submitting an Auger Job

Fri, 10/04/2013 - 14:34 — 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 a new XML based format,
which allows some additional description.

If you are using the traditional file format you submit your job the way that it has always been done with jsub

Description of XML Tags

Fri, 10/04/2013 - 10:45 — chen

The following tags are used inside the Request, Job, and ForEach Tags.
 

Command

The <Command> tag is used to specify the command that will be run on the farm node. It takes its value from the body of this tag. The command may be multiple lines long, or a single line. Note that since this is an XML file, if you want to use XML special characters (in particular < and &), you need to either write them the XML way (< and &) or you can embed your entire command in a CDATA tag. (<![CDATA[ your command ]]>)

srmLs

Fri, 10/04/2013 - 10:43 — ychen

Name

          srmLs - list file properties (cacheManager related meta data)

Syntax

    srmLs cache_path1 cache_path2 cache_path3 ....
    srmLs [options] cache_directory_path

Description

        If no argument is given, lists all larger files on tape but not on disk, owned by this user. Otherwise lists files in a given directory.

XML Command File

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

Introduction

This document describes the specification for the XML based job description language (JDL) that Auger uses.

Language Specification

The JDL is XML based. The top level tag will be a request tag. The submission will consist of a description of one or more jobs that are to be run on the farm. The valid subtags and tag attributes will be described below. The script can be augmented with the use of variables. Comments can be specified by using the XML comments by starting the comments with Tags.

Pages

Powered by Drupal