Overview of Scintillating Plastic Tile Code

After the re-organisation of the multiplicity array code we have the following class for the tiles:

BrTileCalibration

Object to store calibration constants, such as pedestals, gain, and of course the centrality cut functions $S_{cut}(V_z)$.

BrTileCent

Object to store, for a given event, the lower and upper bounds on centrality, as determine by BrTileCentModule.

BrTileCentCalModule

Module to find the functions $S_{cut}$ from many events with BrTileRdo objects in them. This class assumes that a proper vertex cut has been defined, for example using BrVertexFilter and that minimum bias events have been chosen, for example using BrTriggerfilter.

BrTileCentModule

Module to determine the centrality of a given event, based on the input object BrTileRdo and the cut functions $S_{cut}(V_z)$.

BrTileDig

Object⁶ storing the raw digits from the Data Acquisition system (DAQ).

BrTileDigModule

Module⁷ that makes simulated digits from GEANT input.

BrTileGapCalModule

Not complete yet. Module to find the dual range ADC's gap.

BrTileParameters

Object⁸ to store static parameters read from the file $BRATSYS/params/DetectorParameters.txt. Some of it's data members should really be read from a geometry database.

BrTilePedCalModule

Not complete yet. Calibration module to find the ADC's pedestals and pedestal widths. This module assumes that pedestal events have been chosen before hand, for example using BrTriggerFilter.

BrTileRdo

Object⁹ to store calibrated data -- also called a Reduced Data Object.

BrTileRdoModule

Module¹⁰ that makes calibrated data from BrTileDig objects. It assumes that the vertex information is present, as created by some other module e.g., BrRdoModuleBB or BrRdoModuleZDC. Currently, it uses static calibration constants, but is prepared for using calibration constants retrieved from the databases.