Geometry doesn't know about the detector configuration
Right now, functions like DetLength don't take in to account how many diblocks are actively taking data. It would be really nice if Geometry would look at the RunHistory object when it initializes itself to determine the detector length and any other parameters that can change from run to run.
#1 Updated by Christopher Backhouse over 6 years ago
Sounds like there are two parts to this
- Interface with RunHistory to figure out how many blocks there were
- Given this information, figure out the appropriate DetLength from the gdml. Possibly retaining compatibility with the somewhat idiosyncratic answer it gives for the full detector now.
The point is, the second part without the first is still somewhat useful. I imagine a "NumBlocks" parameters in Geometry.fcl is way preferable to whatever hacks are being done now.