GettingStarted hallc replay XEM

Hall C Replay

Purpose

The Hall C replay is a database structure used to hold detector calibrations, detector geometry, detector maps, output templates, replay scripts, defined output histograms, run numbers and run information. You may hear people call this the 'Analyzer' or 'Engine' as the C++ analyzer is based on the earlier ENGINE code written in Fortran. HCANA itself inherits most classes from the Hall A Analyzer. The ultimate goal of the hallc_replay_XEM is to tell hcana how to analyze the raw EVIO files generated by the Hall C DAQ and process them into relevant root branches in a CERN ROOT TFile.

Running Basics

In order to use this structure properly, HCANA must be executed in the top level directory.

• Scripts can be executed by running hcana and typing '.x ./SCRIPTS/<spectrometer>/<run-type>/script_to_run.C'
  • Inside the scripts you will find the way hcana imports all the detector geometry, maps, and calibrations through the gHcParms, which is a THcParmsList object.
• The detector map is loaded into the gHcDetectorMap object, which is a THcDetectorMap object.
  • A cratemap is used to relate detector components (Individual DC wires to TDCs, Hodo PMTs to ADCs, etc) so the detectors can use the signals properly.
• A Spectrometer object is created, and the relevant detectors are added to this spectrometer.
  • The detector geometry and constants are loaded using a DBRequest call in the header of file of each detector class
• Specialized class objects have been created to include information for the trigger, beam, target quantities, and more.