Smoothing egamma material resolution systematic vs pT

Motivation: smoothing egamma material resolution systemaitc which are currently binned values (see plot in jira).

Summary of changes:

• add a swtich `m_interpolate` for linearly interpolating material resolution uncertainty vs pT. Swithced on only for esmodel=es2022_R21_Precision_lowmu
• add a function `interpolateTH1(TH1 *hist, double x, bool abs_bins)` to interpolate linearly in 2 nearest bins with the option to use absolute bin content
• add a function `store_IBL_PP0_YProjections` to projection TH2 to TH1 (for IBL and PP0 systematics) before event loop

tagging ey software conveners @mungo @fnechans, e/y conveners @ludovica @kristin @ahabouel, ey calibration @gunal.

added 21.2 Egamma Recommendation labels

marked this merge request as ready

Build area was cleaned as per request posted in the DB. The full software build will be performed

This merge request affects 1 package:

• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection

This merge request affects 3 files:

• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/ElectronPhotonFourMomentumCorrection/get_MaterialResolutionEffect.h
• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/egammaEnergyCorrectionTool.cxx
• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/get_MaterialResolutionEffect.cxx

added Analysis analysis-review-required review-pending-level-1 labels

WARNING: big files (>100K) are found in the changeset

228K in file PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/egammaEnergyCorrectionTool.cxx

CI compilation and testing are not performed for this legacy branch.

• CI operations are limited to pre-compile checks, setting MR labels, and handling watcher lists.
• Accepted MRs are tested during nightly jobs.

mentioned in merge request !74103 (merged)

added sweep:ignore label

I have added sweep:ignore label since @linghua opened the MR for main as well :-)

Hi @linghua , can you add the ATLAS bot as Developper on your fork, such that the CI status is properly displayed? Thanks

https://atlassoftwaredocs.web.cern.ch/gittutorial/gitlab-fork/#add-your-friendly-build-bot

Best, Lukas - L1

removed review-pending-level-1 label

added review-user-action-required label

added 1 commit

• 82f6ff4a - coding

Compare with previous version

This merge request affects 1 package:

• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection

This merge request affects 3 files:

• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/ElectronPhotonFourMomentumCorrection/get_MaterialResolutionEffect.h
• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/egammaEnergyCorrectionTool.cxx
• PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/get_MaterialResolutionEffect.cxx

added review-pending-level-1 label and removed review-user-action-required label

WARNING: big files (>100K) are found in the changeset

228K in file PhysicsAnalysis/ElectronPhotonID/ElectronPhotonFourMomentumCorrection/Root/egammaEnergyCorrectionTool.cxx

CI compilation and testing are not performed for this legacy branch.

• CI operations are limited to pre-compile checks, setting MR labels, and handling watcher lists.
• Accepted MRs are tested during nightly jobs.