Difference between revisions of "Replay hints for BigBite"

From Hall A Wiki
Jump to: navigation, search
 
m
Line 1: Line 1:
Last update: Mar 28, 2007
+
Last update: Mar 28, 2007
TODO: Keep it updated
+
TODO: Keep it updated
  
-------------------------------------------
+
-------------------------------------------
    README for E04007 ONLINE REPLAY
+
== README for E04007 ONLINE REPLAY ==
-------------------------------------------
+
-------------------------------------------
  
1. Quick Start for Shift Workers
+
1. Quick Start for Shift Workers
  
  
Replay procedures are:
+
Replay procedures are:
  
logon to adaq@adaql<3-?>, call command "goonlana", then "analyzer".
+
logon to adaq@adaql<3-?>, call command "goonlana", then "analyzer".
  
After analyzer is loaded successfully, one can call replay_det() for detector re
+
After analyzer is loaded successfully, one can call  
  play or replay_phys() for physics replay.  
+
replay_det()
 +
for detector replay or
 +
  replay_phys()
 +
for physics replay.  
  
It's also possible to specify the run# and event number in parameters. For ex. r
+
It's also possible to specify the run# and event number in parameters. For ex.  
  eplay_det(1568,1000) will replay first 1k events of run#1568.
+
  replay_det(1568,1000)
 +
will replay first 1k events of run#1568.
  
  
-------------------------------------------
+
-------------------------------------------
  
2. File Locations
+
2. File Locations
  
  
 
The databases directory are:
 
The databases directory are:
bbsoftw@adaqlx:~/DB
+
bbsoftw@adaqlx:~/DB
which is also soft linked to adaq@adaql3:$DB_DIR
+
which is also soft linked to  
 
+
adaq@adaql3:$DB_DIR
  
 
Source of replay scripts used in adaq@adaqlx are located in:
 
Source of replay scripts used in adaq@adaqlx are located in:
bbsoftw@adaqlx:~/<experiment ID>/onlana
+
bbsoftw@adaqlx:~/<experiment ID>/onlana
 
one can get to it by calling goreplay or goonlana macro as bbsoftw.
 
one can get to it by calling goreplay or goonlana macro as bbsoftw.
Key files in above directory are soft linked to adaq@adaqlx:~/e04007/onlana, whe
+
Key files in above directory are soft linked to  
re goonlana is pointed to.
+
adaq@adaqlx:~/e04007/onlana
 +
where goonlana is pointed to.
  
  
Line 40: Line 45:
  
 
replay.C:  
 
replay.C:  
        the replay script. It contains 3 functions:
+
* the replay script. It contains 3 functions:
 
         void replay_phys(Int_t runnumber=0,Int_t all=0)  
 
         void replay_phys(Int_t runnumber=0,Int_t all=0)  
 
     //physics reply  
 
     //physics reply  
Line 59: Line 64:
  
 
def.h:  
 
def.h:  
        a collection of parameters for replay.C.  
+
* a collection of parameters for replay.C.  
      See http://www.jlab.org/~jinhuang/BigBiteDoc/def.h.html
+
* See http://www.jlab.org/~jinhuang/BigBiteDoc/def.h.html
  
 
*.cdef
 
*.cdef
        Cut define
+
* Cut define
  
 
*.odef
 
*.odef
        Out Define
+
* Out Define
  
 
rootlogon.C
 
rootlogon.C
        logon script, load include path, scripts, etc.
+
* logon script, load include path, scripts, etc.
        See http://www.jlab.org/~jinhuang/BigBiteDoc/rootlogon.C.html
+
* See http://www.jlab.org/~jinhuang/BigBiteDoc/rootlogon.C.html
  
 
HallA_style.cxx:  
 
HallA_style.cxx:  
        style sheet
+
* style sheet
  
 
AnaShowRun.C:  
 
AnaShowRun.C:  
        boudle deal of replay() and online()
+
* boudle deal of replay() and online()
  
 
online_C.so->./onlineGUI_v1.2
 
online_C.so->./onlineGUI_v1.2
        complied onlineGUI.
+
* complied onlineGUI.
        See http://www.jlab.org/~moffit/onlineGUI/
+
* See http://www.jlab.org/~moffit/onlineGUI/
  
 
libBigBite.so
 
libBigBite.so
        link to compiled bigbite detector package
+
* link to compiled bigbite detector package
        See http://www.jlab.org/~jinhuang/BigBiteDoc/
+
* See http://www.jlab.org/~jinhuang/BigBiteDoc/
  
 
ReBuildShareObjects
 
ReBuildShareObjects
  Script to rebuild replay_C.so and online_C.so
+
* Script to rebuild replay_C.so and online_C.so
  
  
Line 96: Line 101:
  
  
The idea is bbsoftw@adaqlx maintains the replay files, while adaq@adaqlx can onl
+
The idea is bbsoftw@adaqlx maintains the replay files, while adaq@adaqlx can only use them.  
y use them.  
+
  
Only compiled version of replay.C is auto loaded into analyzer. So, after replay
+
Only compiled version of replay.C is auto loaded into analyzer. So, after replay.C is modified, CALL ./ReBuildShareObjects to rebuild share objects.
.C is modified, CALL ./ReBuildShareObjects to rebuild share objects.
+
  
Do not remove files, backup older files before working on it. A good place is bb
+
Do not remove files, backup older files before working on it. A good place is
softw@adaqlx:~/software/onlana/_SaveOlderFileHer
+
bbsoftw@adaqlx:~/software/onlana/_SaveOlderFileHer
 
+
bbsoftw@adaqlx:~/<experiment ID>/  
bbsoftw@adaqlx:~/<experiment ID>/ holds any file specialized for one experiment.
+
holds any file specialized for one experiment.
All experiment share other file in bbsoftw@adaqlx:~/
+
All experiment share other file in  
 
+
bbsoftw@adaqlx:~/
goonlana and goreplay macro in bbsoftw point to current experiment replay direct
+
goonlana and goreplay macro in bbsoftw point to current experiment replay directory. "Current experiment" is defined in  
ory. "Current experiment" is defined in bbsoftw@adaqlx:~/.bashrc
+
bbsoftw@adaqlx:~/.bashrc
  
 
....
 
....
Line 121: Line 124:
  
 
Production Version
 
Production Version
        is located in bbsoftw@adaqlx:~/software/bigbitelib
+
* is located in  
        it's aimed to run at full speed, although less debug information is outp
+
bbsoftw@adaqlx:~/software/bigbitelib
ut.
+
* it's aimed to run at full speed, although less debug information is output.
        it's default version linked to bbsoftw@adaqlx:~/software/onlana/libBigBi
+
* it's default version linked to bbsoftw@adaqlx:~/software/onlana/libBigBite.so
te.so
+
 
Error Tracing Version
 
Error Tracing Version
        is located in  bbsoftw@adaqlx:~/software_dev/bigbitelib
+
* is located in  
        if Production Version fails, switch to this version. And one can change  
+
  bbsoftw@adaqlx:~/software_dev/bigbitelib
one of the modules to be verbose to trace source of an abnormal. For example, ch
+
* if Production Version fails, switch to this version. And one can change  
ange
+
one of the modules to be verbose to trace source of an abnormal. For example, change
                #define DEBUG_LEVEL  2
+
#define DEBUG_LEVEL  2
        in THaScintPlane.h to higher level (3~5) will outputs more message produ
+
in THaScintPlane.h to higher level (3~5) will outputs more message produced in analysis of Bigbite Trigger Plane data.  
ced in analysis of Bigbite Trigger Plane data.  
+
 
        Notice: a "make" and modifying soft link bbsoftw@adaqlx:~/software/onlan
+
Notice: a "make" and modifying soft link  
a/libBigBite.so are necessary for taking effect.
+
bbsoftw@adaqlx:~/software/onlana/libBigBite.so  
 +
are necessary for taking effect.
  
 
For more info, please visit http://www.jlab.org/~jinhuang/BigBiteDoc/
 
For more info, please visit http://www.jlab.org/~jinhuang/BigBiteDoc/

Revision as of 22:05, 31 March 2008

Last update: Mar 28, 2007 TODO: Keep it updated


README for E04007 ONLINE REPLAY


1. Quick Start for Shift Workers


Replay procedures are:

logon to adaq@adaql<3-?>, call command "goonlana", then "analyzer".

After analyzer is loaded successfully, one can call

replay_det()

for detector replay or

replay_phys()

for physics replay.

It's also possible to specify the run# and event number in parameters. For ex.

replay_det(1568,1000)

will replay first 1k events of run#1568.



2. File Locations


The databases directory are:

bbsoftw@adaqlx:~/DB

which is also soft linked to

adaq@adaql3:$DB_DIR

Source of replay scripts used in adaq@adaqlx are located in:

bbsoftw@adaqlx:~/<experiment ID>/onlana

one can get to it by calling goreplay or goonlana macro as bbsoftw. Key files in above directory are soft linked to

adaq@adaqlx:~/e04007/onlana

where goonlana is pointed to.


Replay directory contains following files:

replay.C:

  • the replay script. It contains 3 functions:
       void replay_phys(Int_t runnumber=0,Int_t all=0) 
   //physics reply 
       void replay_det(Int_t runnumber=0,Int_t all=0) 
   //detector reply 
       void replay(Int_t runnumber=0,Int_t all=0, 
           Int_t ReplayMode=kReplayBigBiteTp, 
           Int_t DefReplayNum=-1, 
           char* OutFileFormat=OUT_FILE_FORMAT 
           ) 
   //general replay script 
       See http://www.jlab.org/~jinhuang/BigBiteDoc/replay.C.html
   There are also more replay script to replay Left or right HRS only:
        replay_det_R (<run#>,<Event #>)
        replay_phys_R(<run#>,<Event #>)
        replay_det_L (<run#>,<Event #>)
        replay_phys_L(<run#>,<Event #>)

def.h:

  • .cdef
  • Cut define
  • .odef
  • Out Define

rootlogon.C

HallA_style.cxx:

  • style sheet

AnaShowRun.C:

  • boudle deal of replay() and online()

online_C.so->./onlineGUI_v1.2

libBigBite.so

ReBuildShareObjects

  • Script to rebuild replay_C.so and online_C.so



3. Maintenance Guideline


The idea is bbsoftw@adaqlx maintains the replay files, while adaq@adaqlx can only use them.

Only compiled version of replay.C is auto loaded into analyzer. So, after replay.C is modified, CALL ./ReBuildShareObjects to rebuild share objects.

Do not remove files, backup older files before working on it. A good place is

bbsoftw@adaqlx:~/software/onlana/_SaveOlderFileHer
bbsoftw@adaqlx:~/<experiment ID>/ 

holds any file specialized for one experiment. All experiment share other file in

bbsoftw@adaqlx:~/

goonlana and goreplay macro in bbsoftw point to current experiment replay directory. "Current experiment" is defined in

bbsoftw@adaqlx:~/.bashrc

....


4. Big Bite Library


There are two version of Big Bite Library for choice.

Production Version

  • is located in
bbsoftw@adaqlx:~/software/bigbitelib
  • it's aimed to run at full speed, although less debug information is output.
  • it's default version linked to bbsoftw@adaqlx:~/software/onlana/libBigBite.so

Error Tracing Version

  • is located in
bbsoftw@adaqlx:~/software_dev/bigbitelib
  • if Production Version fails, switch to this version. And one can change

one of the modules to be verbose to trace source of an abnormal. For example, change

#define DEBUG_LEVEL   2

in THaScintPlane.h to higher level (3~5) will outputs more message produced in analysis of Bigbite Trigger Plane data.

Notice: a "make" and modifying soft link

bbsoftw@adaqlx:~/software/onlana/libBigBite.so 

are necessary for taking effect.

For more info, please visit http://www.jlab.org/~jinhuang/BigBiteDoc/