Non-deterministic jet algorithm checksums
While testing checksums in the context of !2757 (merged), I encountered non-deterministic checksum behavior from a few Jet selection algorithms present in both HLT2 and Sprucing. These are: TagsSimpleJets, JetBuilderSimpleJets and WJetEEMerger. My only lead is that the "Fit aborted" warning occurs one time extra in one of the runs.
JetBuilderSimpleJets_1e416068.Mo... SUCCESS #WARNINGS = 50 Message = 'MassErr^2 < -999 -> Fit aborted'
JetBuilderSimpleJets_1e416068.Mo... SUCCESS #WARNINGS = 49 Message = 'MassErr^2 < -999 -> Fit aborted'
\
Full logs of 100k Sprucing is available at: /eos/user/d/dmagdali/checksum_logs/. With runs with "old" and "new" configuration run at different times. Will add HLT2 logs as well.