Difference between revisions of "Off Line Analysis for transversity"

Revision as of 06:21, 14 February 2009

This is temporary site of Off Line Analysis for transversity.

Farm Replay

Structure

HowTo do a quick test replay

One can directly use the common replay directory to do quick tests.

ssh ifarml5    # or any computer seeing working disk
cd /w/work5602/transversity/replay
source replay.sh
cd replay
analyzer
replay_phys(4029,100000);   //just like online replay

HowTo build your own batch farm replay directory

Build a directory for your own replay. You can change replay code and control the rootfile storage. And it will be capable of replaying on both ifarm and batch farm.

ssh ifarml5    # or any computer seeing working disk

cd /work/halla/transversity/disk1/<your name>

mkdir analysis    # this is the main directory for replay codes
cd analysis

cp -rv /work/halla/transversity/disk1/replay/replay  ./
cp -rv /work/halla/transversity/disk1/farmreplay ./
cp -rv /work/halla/transversity/disk1/replay/replay.sh ./

mkdir /work/halla/transversity/disk3/<your root file folder>
ln -svf /work/halla/transversity/disk3/<your root file folder> ROOTfiles

Now you have the basic structure:

• To test replay on ifarm, follow Off Line Analysis for transversity#HowTo build your own replay directory
• To do batch farm replay, follow example below:
  1. enter directory farmreplay
  2. edit construct.pl, modify following sections:
     • $neve : the event number to replay
     • @runnumber : list of run to replay
     • $ReplayType : name of replay script
     • $current : path of your analysis directory
  3. run construct.pl; it will generate
     1. in_run# : the script for batch running for each run; check it carefully
     2. sub_run# : Batch Job Command File for each run; check it carefully
  4. (Optional), test in_run# scripts by copying it to a tmp directory and run it.
  5. jsub sub_run# will run the replay in batch farm

General Rule for Farm Disk Usage