Difference: LHCbID (7 vs. 8)

Revision 82008-09-19 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="EventModelReview"

LHCbID Class

Line: 8 to 8
  LHCbID is a class that provides a single generic channel identifier throughout LHCb. It is mainly used by the (new) track model to uniquely identify the measurements that were used to make the track. Given a list of LHCbIDs and the corresponding measurements (that can be regenerated trivially from the RawBuffer), it should be possible to reproduce the results of the track fit.
Changed:
<
<
The main requirement when designing this class was that it should be possible to construct from (and to get back) the individual sub-detector channel IDs (VeloChannelID, ITChannelID, OTChannelID, RichSmartID, MuonTileID). The detector specific part is coded on 28 bits, leaving 4 bits to identify the sub-detector. The detector specific part is further sub-divided into a "Specific" part that stores the information necessary to rebuild the channel ID, and a detector dependent number of "Spare" bits that contain additional detector specific information (for example the chosen solution for the Outer Tracker left-right ambuguity)
>
>
The main requirement when designing this class was that it should be possible to construct from (and to get back) the individual sub-detector channel IDs (VeloChannelID, STChannelID, OTChannelID, RichSmartID, MuonTileID). The detector specific part is coded on 28 bits, leaving 4 bits to identify the sub-detector. The detector specific part is further sub-divided into a "Specific" part that stores the information necessary to rebuild the channel ID, and a detector dependent number of "Spare" bits that contain additional detector specific information (for example the chosen solution for the Outer Tracker left-right ambuguity)
 
Changed:
<
<
LHCbID is currently not implemented for MuonTileID. This is mainly due to packaging problems (introduction of a circular dependency between LHCbKernel and MuonKernel packages) which could not be easily solved due to the rather complex dependency structure of the MuonKernel code. The review should give suggestions on how to resolve this issue.
>
>
LHCbID is currently not implemented for MuonTileID. This is mainly due to packaging problems (introduction of a circular dependency between LHCbKernel and MuonKernel packages) which could not be easily solved due to the rather complex dependency structure of the MuonKernel code. The review should give suggestions on how to resolve this issue.
 
Changed:
<
<

Doxygen Documentation

>
>

Documentation

 
Deleted:
<
<
  -- MarcoCattaneo - 15 Jul 2005
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback