GTR package to combone subdetectors (package gtrmix)
27nov00 1220
Code version 0.21
D0 global tracking is described at
http://www.bonner.rice.edu/adams/d0/gtr
Links to code
The description below includes links to the code contained in this
package. This
version
of the code may not be the most recent.
Description
Package gtrmix introduces classes that combine detector subsystems
and the D0 geometry system.
No framework packages are defined.
The physical components include:
- GtrSystem(
header,
source,
test )
- GtrDetector(
header,
source,
test )
- register_gtrmix_types(
header,
source,
test )
- GtrMsDetector(
header,
source,
test )
- GtrTrfDetector(
header,
source,
test )
- GtrDetectorFiller
header,
source,
test )
Their dependencies are illustrated in the
physical dependency diagram. [does not exist]
The class diagram [does not exist]
shows the classes and their relationships.
This package depends on the following external packages:
The following sections describe the main programs and the classes defined
in the components. Unless otherwise, noted each class is defined in the
component of the same name.
The descriptions here are brief.
See the header files for details.
GtrSystem
The component GtrSystem defines the compile flags specifying which
detector subsystems (CFT, SMT, ...) are enabled, i.e. are
included in compiling an linking. Class GtrSystem reports which
are enabled. Objects of that type are then used to specify the subset
of these that are active at run time.
register_gtrmix_types
A function which registers all the objstream types used by TRF++ and
each of the enabled subdetectors.
GtrDetector
Class GtrDetector defines the global detector by combining simple
subdetectors which do not account for material. Class GtrMsDetector
does the same but accounts for mutiple scattering.
GtrDetectorFiller
GtrDetectorFiller is the global detector filler. It makes use of each
of the subdetector fillers.
GtrTrfDetector
Class GtrTrfDetector creates and provides access to single version of
the detector for the GTR system. The detector is created when the first
request is made. This request may be made with an RCP specifying the
detector subtype and parameters. If no RCP is specified, then the default
detector is generated.
Questions or comments to dladams@fnal.gov.