Running on the farm

D. Adams
05jul01 1640

Use

fbs -help

for instructions for running on the farm. In particular

fbs status -u d0fgtr

will list jobs submitted from our account. Or see the GreenQ or BlueQ.

The FBS user's guide amy be found at http://www-isd.fnal.gov/fbsng/version_1.3/users_guide/users_guide.html.

You may need a kerberos ticket to submit batch jobs. Use the command

kinit dladams

substituting your username. Also make sure you are listed in ~/.k5login.

Here are instructions for running the global tracking executable gtr on the D0 FNAL Linux farm.

Log into the account d0fgtr on d0bbin.

Create a subdirectory with your user name if you have not already done so. Anything you install should go in this area:

> mkdir /d0/stripe4/d0fgtr/dladams

Use your FNAL username -- not dladams as in the example.

Choose a name for the set of runs. For this example I choose t121_test. Copy the template run directory to that name somewhere in your area. This is the run control directory.

> cp -r /home/d0fgtr/run/template /d0/stripe4/d0fgtr/dladams/t121_test
> cd /d0/stripe4/d0fgtr/dladams/t121_test

Define your release locations in the file srtenv.sh in the example subdirectory. Choose a public release from /home/d0fgtr/releases. You may want to use a private release from that same area or use one from your own area. If you leave the private release blank, you will use the public release only.

Typically the public releases are not optimized and the private releases have full compiler optimization.

You may want to modify runenv.sh if you do not want the default run conditions.

This directory will be used as the template for all runs. Step up to the run control directory. The directory infiles contains files which the list input files for a series of standard run names. If you want to run one of these, use the submit command:

> submit pzmm0-1

In the run directory, the file farm.log will show you what is running. Standard and error outputs are in /home/d0fgtr/logs with file names including the job number. After the job is complete these will be moved to the run directory with the names farmout.log and farmerr.log. During the run, farmstat will show the number of lines in evid.log. This is one more than the number of processed events.

dladams@fnal.gov