For specific information on any of the MuID classes or functions, please see the source documentation.
Figure 1. Class structure of the MuID offline data objects. The diagram uses the Unified Modeling Language (UML) notation.
Data classes
Objects of these class types contain the MuID data. The objects are kept on the PHOOL data tree while a chain is running. These classes are identified by a "dMui" or "TMui" prefix: "dMui" specifies a STAF-style table, while "TMui" is used for any class type.
Geometry and address classes
These classes, TMuiGeometry and TMuiAddressTable, manage the geometry and address data, respectively, and provide a convenient interface to the data. The data are retrieved from external data files or from the PHENIX Objectivity database.
Parameter classes
These classes contain the parameters that control the operation of the various modules. They are typically STAF-style tables (with a "dMui" prefix), and can be identified by the "Control", "Ctrl", or "Par" in the class name.
Module classes
These classes are responsible for operating on the data. They are identified by the "mMui" prefix.
Utility classes
The source code for the MuID offline software can be found in the PHENIX CVS repository, in the directory offline/packages/mui.
The repository can be viewed from the Web using the CVS source browser.