DefaultDigitizer: Threshold Polarity
Currently, we just call std::abs(Pixel_charge->getCharge())
in the DefaultDigitizer. This is problematic because transient simulations might provide PixelCharge
objects with different polarities, e.g. a central pixel with a large negative charge accumulated (say, -800e) and neighbors with small positive charge induced (say +30e). Both are currently treated the same bu the front-end and are seen as valid inputs with "correct" polarity.
We might have to introduce a threshold polarity setting here - which will break backwards compatibility.