classID for LHCb detector description

When creating detector elements with standard convertors, the classID assigned is = 2. When creating detector elements with specialized convertors (like DeRich1) one needs to assign a unique number, within the conventions recomended. The recomended ranges for the classID for each sub detector are listed below.

Sub-Detector	Class ID range	Comments
Velo	8100 - 8399	(avoid overlap with existing OT and other detectors)
Velo upgrade	8200 - 8399
RICH	12001 - 12094
TT	9100 - 9199
ST	9200 - 9399
OT	8400 - 8499
FT	8600 - 8699
Calo	8900 - 8999
Muon	11000 - 11099
Bcm	14000 - 14099

The classIDs assigned so far, in LHCb software as of May 24-2012 are listed in a dedicated table. So when you assign a new classID, please ensure that it is within the range recomended above and that within that range, it is not one of the numbers in the table.

It turns out that the Velo and OT shared the same range in the past although it is not recomended any more. Hence when creating the classID for Velo upgrade, one should also verify that the new numbers are not same as those from the exisiting OT. This can be verified looking at the extended table

Please also let us (lhcb-gauss-manager@cernNOSPAMPLEASE.ch) know the classID numbers you assign. We shall then update the extended table. This is so that other people in the future knows to avoid that number. This is of special importance to people creating detector descriptions for LHCb upgrade.

-- SajanEaso - 25-May-2012