DetectorHistogrammer: shift global hit map boundaries to global position of sensor
Title says it all. Fix for forum entry.
Before I mark this as ready, I'd like to throw in two remarks:
- This is the minimalist approach. With the initial implementation here (SensorCenter +- SensorSize/2), we display all hits, but in case of larger rotations, the axis ranges might be unnecessarily large. Should we scale by the cosine of the rotation?
- The hits in global coordinate systems are of course distributed over a 3D space and the global hitmaps show projections. Do we see a benefit in adding xz and yz projections?