On-line C++/Root Analysis hints for DETECTOR and PHYSICS Replay

Updated April 26, 2004

For DETECTOR REPLAY:

   1. Login to adaql5 as "adaq" account.

   2. Type "goonlana"   (without the quotes)

      (This takes you to directory ~/$EXPERIMENT/onlana

       and sets $DB_DIR environment variable).

   3. Type "analyzer"   (without the quotes)

   4. At the analyzer prompt, type ".x detReplay.C"

      and don't forget the dot(.) before the x.

      You will be asked for the run number AND for the number of events

      to analyse. Usually a reasonable number is 20000 (or more)

      Speed of replay is roughly 100 Hz (quite low also due to the large

      number of histograms in output)

   5. After the analysis is done (step 4), type

      the following either at the analyzer prompt 

      or in a separate root session.

          .x online.C+("detectorL")

          .x online.C+("detectorR")

          .x online.C+("detphysics")

   6. COMPARE with REFERENCE plots

For PHYSICS REPLAY (when in production):

   1. Login to adaql5 as "adaq" account.

   2. Type "goonlana"

      and then go into the directory ../ana :

      cd ../ana

   3. Type "analyzer"   (without the quotes)

   4. At the analyzer prompt, type ".x physReplay.C"

      You will be asked for the run number AND for the number of events

      to analyse. 

      For production data shift workers should analyse ALL events, so

      type "-1".

      Speed of the physics replay is roughly 300 Hz (for now), so that 

      a "typical 800K events run" takes approximately 45 min. to be analysed.

      It is therefore important to start this analysis as soon as a run

      is ended.

   5. After the analysis is done (step 4), you can have a quick look 

      at the results by typing the following in a separate C++ analyzer 

      session running in the "ana" work directory: 



      .x online.C+("physics",runnumber) 



      "runnumber" must be replaced by the number of the run that you want to 

      look at. The online.C command will not work without the second 

      argument when you are in the "ana" directory. Also, the online.C 

      command will not work properly if you run it in the same C++ analyzer 

      session as the physReplay.C script.

   6. COMPARE with REFERENCE plots

   7. Edit the file "runlist" and add the list of runs you are analyzing

   8. Since each physReplay takes more than 40 minutes, more runs can be

      analysed in parallel from the same directory (ana) by logging in

      on different machines (adaql4, adaql5, happex5).

      Since adaql5 is multiprocessor, multiple runs can also be replayed

      from adaql5.

   9. Do not edit a different "runlist" file in the ana2 directory, just 

      continue to fill the "runlist" file on ana1