Sanitise properties of CaloShowerOverlap
The following discussion from !2080 (merged) should be addressed:
-
@cmarinbe started a discussion: (+1 comment) shouldn't we always use m_etMin as last and m_etMin2 as last2? Otherwise the definition of these properties is misleading. If the user mistakenly (or not) sets m_etMin > m_etMin2 we can rise a warning or something but changing their usage without any message looks dangerous