Cannot get consistent results for S28r2 and S34r0p1 locally
Relates to DV too
In stripping24r2-28r2-patches
- S24r2 is fine
- S28r2 cannot give consistent counters locally (ie. running the test twice produces different counters). The differences are small and do not affect the rates etc.
PhotonHighSelZ0RareDecay ref) "# Phys/StdLooseAllPhotons" | 797 | 29295 | 36.757 | 17.512 | 1.0000 | 108.00
(PhotonHighSelZ0RareDecay new) "# Phys/StdLooseAllPhotons" | 797 | 29301 | 36.764 | 17.515 | 1.0000 | 108.00
Look at the differences in the lines btw S24r2 and S28r2?
In 2018-patches
- S34 is fine
- S34r0p1 cannot give consistent counters locally
So its not a stack thing and not a rerunning the CALO thing.
Marco suggests it could be uninitialised pointer? Floating point number assigned wrong?
Test 2018-patches
reproducibility by running high statistics tests tests twice:
- S28r2: 60k test no rate difference
- S34r0p1: 100k test no rate difference
- S34: 100k test only 0.001% rate difference in StrippingZVTOP_High_Line
Edited by Alison Maria Tully