Unexpected ROI behaviour for DUT efficiency calculation
What's the reason for this? https://gitlab.cern.ch/corryvreckan/corryvreckan/-/blob/master/src/modules/AnalysisEfficiency/AnalysisEfficiency.cpp#L278
It means that only the following histograms are filled if the track lies within the ROI:
- hPixelEfficiencyMap_trackPos_TProfile and hPixelEfficiencyMap_trackPos
- eTotalEfficiency
- efficiencyColumns and efficiencyRows
For all other histograms the ROI is ignored. This does not become evident from the README, and I'm now wondering, why implemented this behaviour...can anyone remind me?