Integrating QA Histograms into Makers

(Instructions provided by Gene Van Buren, November 17, 2004)

It is generally the responsibility of the subsystem software leaders to select the appropriate histograms for quality assurance studies of the data and to integrate those histograms into their event reconstruction Makers. The following are some helpful instructions provided by Gene Van Buren for integrating QA histograms into subsystem Makers. This process involves a collaborative effort between the subsystem software expert and Gene Van Buren.

There are two possible ways to do this:

1) Create the histograms in your own Maker, use
StMaker::AddHist() on them, and tell me (Gene Van Buren) what your
maker is called.

2) Write up the code that would be necessary to produce
the histograms from StEvent and give it to me. This option
only works if your data is available in StEvent, but allows
reproduction of the histograms from event.root files as
well as during production.

If you have no preference, the QA team recommends
option 1 because it leaves maintenance of the histograms
(for the most part) in your hands. But we will work with
either option given your preference.

After that, there are two more issues:

a) Do you want the histograms to be viewed by the QA
shift crew? Such histograms are a subset of the total set of
QA histograms. The rest can be viewed by more interested
experts at any time. Please be very conservative in selecting
histograms for the QA shift crew to review; a few well 
chosen plots are optimal.

b) Do you want the histograms to be viewed by trigger type
or not? For most histograms in QA, we make separate
instances of the histograms for different trigger sets (for
example, central triggers, minbias triggers, high tower
triggers, etc.). This is only available with option 2) above.
Some histograms have only one instance, filled for all
trigger types of interest in each file sequence.

Lastly, we can add colors or lines or log axes or whatever
graphics you'd like when the plots are drawn.