Adding an AppraisePulseFinder module which will, somehow, quantify how "good" a pulse finder is. At the moment, you supply a detector name and a pulse number (which you can get by running MakeAnalysePulse with plot_pulse = true in TVPulseFinder) and it will plot that pulse. More to come...
Add an associated PulseFinder to test. At the moment need to repeat the MakeGenerator() code from MakeAnalysedPulses. Is there any way to avoid this?
Realised I was still getting overflow in CaUH/Ge-S because I wasn't subtracting 1 from the max digitised sample