Difference between revisions of "Off Line Analysis for transversity"

From Hall A Wiki
Jump to: navigation, search
(Usefull Links)
Line 36: Line 36:
 
analysis directory could be copied to your own location to be customized.
 
analysis directory could be copied to your own location to be customized.
  
==== Usefull Links ====
+
 
* [http://scicomp.jlab.org/scicomp/ Auger/Jasmine web pages]
+
* [https://wiki.jlab.org/cc/external/wiki/index.php/Scientific_Computing Scientific Computing Wiki]
+
* Experiment [[Transversity]]
+
  
 
=== HowTo do a quick test replay ===
 
=== HowTo do a quick test replay ===

Revision as of 06:56, 14 February 2009

This is temporary site of Off Line Analysis for transversity.

Farm Replay

Structure

On farm file system, there are 3 disk:

  • disk1 : Our main script disk.
  • disk2 : Shared with E08007, mostly full
  • disk3 : 2TB disk for large root files

THe main analysis directory is /work/halla/transversity/disk1/analysis/, which includes various of components:

  • replay.sh = SourceMeFirst : script setting up environmental pathes. Configured for CSH
  • replay : replay directory holding replay scripts/configure files
  • farmreplay : specialized folder generating batch farm replay scripts
  • DB : database
  • analyzer : analyzer
  • bigbitelib : Bigbite library
  • RICHlib : rich lib
  • BBNormAna : Normalization analysis lib
  • onlineGUI : Online GUI

analysis directory could be copied to your own location to be customized.


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 /work/halla/transversity/disk1/analysis
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/analysis/replay  ./
cp -rv /work/halla/transversity/disk1/analysis/farmreplay ./
cp -rv /work/halla/transversity/disk1/analysis/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; double check it carefully
      2. sub_run# : Batch Job Command File for each run; double 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

HowTO Customize Analyzer / Libs / Database

There are more folders in /work/halla/transversity/disk1/analysis/, which are various of components:

To use your own version of components, first copy its direcory to your own analysis folder, then

  • for database and analyzer, modify your replay.sh to set its path
  • for other libraries, just modify the *.so link in your replay directory to your own location

General Rule for Farm Disk Usage