Skip to content

Preparing the FFJetSmearingTool for UFO jets in R22+

Daniel Camarero Munozrequested to merge
(removed):main into main

Several new functionalities are included since we need to apply jet mass resolution (JMR) uncertainties to physics analyses in R22 Phase-I large-R pre-recommendations. Up until now the tool did only work for LCTopo jets and some aspects required an update. A summary is provided below:

  • The changes do only affect the programs JetUncertainties/Root/FFJetSmearingTool.cxx and JetUncertainties/JetUncertainties /FFJetSmearingTool.h
  • A new mass definition "UFO" has been added, and I made changes to avoid needing to prive the Calo and TA mass weight histograms via config file
  • The tool can now support various MCTypes now (similar feature used in JetUncertainties tool) [flag: SupportedMCTypes]
  • The tool can now interpret PtAbsMass (was already able) and eLOGmOeAbsEta (new) uncertainty parameterisations [provided as input via config file: JMRComponent.#.Param:]
  • The tool does now apply a Gaussian smearing by default, and can be easily configured via config file to perform the standard FF smearing [flag: doGaussianSmearing] providing the response maps [flag: ***ResponseMap, where *** depends on the jet collection used]
  • Aesthetic changes to improve readability and consistency of different code sections are implemented. These are not necessary but improve the clarity and I think will help with preserving the code for the future.

I have performed validation tests using AB release 25.2.4 and MC DAOD_PHYS dijet derivations (from mc20_13TeV.600627.PhPy8EG_jj_JZ4.deriv.DAOD_PHYS.e8351_s3681_r13167_p5855). Some cross-checks performed:

  • The code runs well for different MCTypes: MC20, MC21, and MC23
  • The code interpretes correctly the different uncertainty parameterisations: PtAbsMass and eLOGmOeAbsEta
  • The doGaussianSmearing is also validated providing the response maps for testing
  • The uncertainty shifts propagated by the tool are the expected
  • I have run over 20000 events and I don't see any issue or warning related to my implementations

Tagging @dmelini, @mdiamant, @camacho, and @fballi

Merge request reports