Detector ID assignments
From Moller Wiki
Revision as of 15:08, 18 September 2018 by Wdconinc (Talk | contribs) (Created page with "== Detector ID assignments: Current and Proposed Scheme == Virtual planes: * Proposed [1,100[ (i.e. keep 28) Target geometry: * 1 in targetDaughter_Clamshell_Optimized*.gdml...")
Detector ID assignments: Current and Proposed Scheme
Virtual planes:
- Proposed [1,100[ (i.e. keep 28)
Target geometry:
- 1 in targetDaughter_Clamshell_Optimized*.gdml
- [6003,6008] in targetDaughter*.gdml
- Proposed [100,200[
Hall geometry:
- [99,109],6000 in hallDaughter_merged.gdml
- Proposed [200,300[
Upstream toroid:
- 2002,[4001,4007] in upstreamDaughter.gdml
- 200,[2000,2006],[4001,4007],[6010,6012] in upstreamDaughter_*.gdml
- Proposed [300,400[
Hybrid toroid:
- [3001,3014],[2001,2005] in hybridDaughter.gdml
- [3001,3014],201,[2003,2004],[6020,6032] in hybridDaughter_merged.gdml
- [3001,3014],201,[2003,2004],[6020,6032] in hybridDaughter_noShlds.gdml
- Proposed [400,500[
Tracking detectors:
- {501,502,503,504} in daughterGEM{1,2,3,4}.gdml
- 30 in trackingDaughter.gdml
- Proposed [500,600[
Main detector segments:
- [1000, 7000[ in detector_parametrized.gdml
- 28 in detectorDaughter*.gdml
- Proposed [1000,7000[
Showermax detector:
- Not implemented
- Proposed [7000,8000[
Pion detector segments:
- {4000,4001,4010,4011,4020,4030,4031} in pionDetectorLucite.gdml
- 4002 in pionDetectorGEM.gdml
- 4003 in pionDetectorTS.gdml
- [4004,4005] in pionDetectorCalorimeter.gdml
- {4060,4061} in pionDetectorVirtualDet.gdml
- Proposed [8000,9000[
Dump geometry:
- [6,25],51 in dumpDaughter.gdml
- Proposed [900,1000[
Others (unregulated):
- detector_mainz.gdml: > 50000
- Proposed [10000,infinity[