Unix Farming Procedures

A scheme has been defined to describe simulation 'tasks' and to submit arbitrary numbers of batch jobs based on the task description. The description is contained in a .task file which contains everything that needs to be known about the task.

Sample task file for Isajet 7.37 WW Standard Model backgrounds:

Item Value Description
Task: ij737-WW task name; also name of directory containing task data
Setup-file: $FARMSYS/ij737-WW/setup-environ unused for now
Gen-BatFile: $FARMSYS/ij737-WW/isajet-bat script to submit generator jobs to batch
Detector-ini: $FARMSYS/ij737-WW/Detector.ini geometry file
Nld-generator: HepEvt 2 choices: HepEvt (StdHep file) or NBeam (diagnostics)
Generator-ini: $FARMSYS/ij737-WW/wpair.car generator parameter file
Run-Period: 1 500 range of runs to submit
RndmBlock: 2 sets random seed
Requested-Events: 100  
Generator: ij737 name of exe
Generator-Task: ij737-WW name of task that supplies generator input
Sim-Code-Version: $NLDROOT/gismo/ top of simulation code tree
Gen-Code-Version: $NLDROOT/isajet/bin/ location of generator exe
Architecture: all unused
Input-disk: /nfs/surrey02/nld/ij737-WW/ where generator output files go
Output-disk: /nfs/surrey02/nld/ij737-WW/reference/ where simulation output files go
Comments: IsaJet SUSY Standard Model W Pairs  

 
Task information is gathered together in a directory with the same name as the task. The FARMSYS environment variable is set to the directory containing the task directories. One job per run number will be submitted.

Use

See the zips area for tar.gz archives of the Perl scripts. The tar file contains the simulation submission and batch files, the generator submission file and one sample generator batch file.

Note: the batch submission scripts assume the LSF batch system! If your are not using LSF, you'll need to modify the xxx-bat files to submit appropriately.


R.Dubois Last Modified: 01/13/04 12:55