As of the tag "HitMaps" in the master branch, the Hall C++ analyzer will read Hall C style CTP parameter files, and read a Hall C data file and sort HMS hodoscope data and HMS drift chamber data into Hall C style hit lists. It will also fill global variables from which hodoscope hit maps can be created.
Code analysis software
- Cppcheck is a static code analysis tool.
- Valgrind is a an instrumentation framework for building dynamic analysis tools.
If you don't already have a copy of the Hall C Analyzer git repository, go to Analyzer/Git to set it up.
To make sure your git repository is up to date, do
in the top hcana directory. After doing this type:
If it complains that podd is modified or not up to date, then type
git submodule update
Decoding hodoscope and drift chamber hits
To demonstrate the analyzer decoding hits, retrieve the file daq04_50017.log.0.gz into the "examples" subdirectory and run "gunzip daq04_50017.log.0.gz" to uncompress the data file. (If you want to use a different data file, edit the "THaRun" line in hodtest.C to point to the run file name). After making sure the analyzer is cleanly compiled, from "examples" do:
../hcana .x hodtest.C
hodtest.C is a script that sets up an analysis. Annoted hodtest.C explains the current version of this script.
Look in podd/examples for Hall A analyzer script examples.
To see hits printed out by the analyzer, edit hodtest.C and comment out the line
HMS->AddDetector( new THcDriftChamber("dc", "Drift Chambers" ));
before running the script. To see hodoscope hits, uncomment some code at the end of the THcHodoscope::Decode method.
Running this script will create a root file, "hodtest.root." The contents of this file are controled by "output.def". (See hcana/podd/examples/output_example.def for examples of how to make an output definition file.)
To see the histograms that were created, do:
../hcana .x hitmaps.C
which should make this plot:
The analyzer does nothing Hall C specific beyond printing hits and filling the hitmap histograms. But it does serve as an example of how to decode hits for other detectors and as a starting point for writing detector analysis code.
To try just reading parameters, run the analyzer from the top directory.
Once it starts up, type
To dump the parameters read
Some examples of accessing individual variables
analyzer  Double_t ProtonMass = *(Double_t *)gHcParms->Find("proton")->GetValuePointer(); analyzer  ProtonMass (Double_t)9.38272000000000048e+02
analyzer  Int_t *integerarray = (Int_t *)gHcParms->Find("integerarray")->GetValuePointer(); analyzer  integerarray (Int_t)4