AnalysisTop: Disable FFJetSmearingTool when running nominal-only
This is a work-around which disables the initialization of the FFJetSmearingTool for jet mass resolution uncertainties, when not running systematic uncertainties. Under normal circumstances, we don't have to resort to such actions, but this tool consumes significant amount of memory (~2GB). The issue with the tool is being followed-up with JetEtMiss experts.
Merge request reports
Activity
added 21.2 Analysis AnalysisTop + 1 deleted label
added JetEtmiss analysis-review-required review-pending-level-1 labels
CI Result SUCCESS (hash cb5d3363)AnalysisBase AthAnalysis externals cmake make required tests optional tests Full details available on this CI monitor view
AnalysisBase: number of compilation errors 0, warnings 0
AthAnalysis: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 35974] CI Result SUCCESS (hash cb5d3363)AthDerivation externals cmake make required tests optional tests Full details available on this CI monitor view
AthDerivation: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-GCC62-CC7 927]removed analysis-review-required label
added analysis-review-approved label
mentioned in commit b9dccb95
added sweep:done label
added sweep:failed label
mentioned in commit omajersk/athena@c0248749
mentioned in merge request !44712 (merged)