Page History

...

The volIds for the ribbons were updated to provide for the new segments in the x top and side ribbons. The ribbon id's are formed with 6 fields (in xmlGeoDbs v1r39p3):

1. Wiki Markup\[0\] field = fLATObjects, value = eLATACD(=1)unmigrated-wiki-markup
2. \[1\] field = fACDFace, value in the range \ [0,4\]. The negative X face is 1, then continue counterclockwise in numbering the remaining side faces.
3. Wiki Markup\[2\] field = fACDCmp, value = eACDRibbon (= 41)
4. Wiki Markup\[3\] field = fMeasure, value = eMeasureX (resp. eMeasureY) for ribbons whose short dimension  is parallel to short dimension  is parallel to x-axis (resp. y-axis).unmigrated-wiki-markup
5. \[4\] field = fRibbon, values in the range \ [0, 3\].unmigrated-wiki-markup
6. \[5\] field = fSegment. Value is always 0 for side faces. For x-measuring top ribbons (whose continuation runs along \ +Y and \ -Y faces) range is in \ [1, 5\] for normal segments under top tiles. Value = 6 for extra little pieces of ribbon behind vertical part of top bent tiles. y-measuring top ribbons are modeled with a single volume, fSegment = 1.

So, in particular, the side ribbons are /1/<face (1-4)>/41/<meas-direction>/<ribbon # (0-3>/0

...

 Running detCheck on xmlGeo v1r39p3 and v1r42
IdMap from v1r39p3  and  v1r42

Updates for AcdDigi

The introduction of additional fSegment values does not require any changes to idents or AcdDigi.  In those contexts we are strictly interested in detectors, not so much individual volumes.  AcdIds are detector-level identifiers and the volume ids when used in an AcdId ctor, are stripped of any segmentation information.  AcdDigi searches the geometry during initialization to locate all ACD detectors.  This search uses the volume names to pick out volumeIds of interest.  This bit does have to be modified, due to the new naming organization of the ribbons.