Skip to content

Disable copy of SF in SelectorAlg

Thomas Strebler requested to merge tstreble/easyjet:SelectorAlg_SFskip into main

The object SelectorAlg had so far a copy of the SF needed for the view containers created. This was found to be necessary to access the SF with the view containers, when running with systematics in downstream algorithms, e.g. in

https://gitlab.cern.ch/easyjet/easyjet/-/blob/main/bbttAnalysis/src/BaselineVarsbbttAlg.cxx#L194

For nominal, this is not needed. It's not clear why this is needed for systematics.

In any case, the copy of the SF has the downside that when running with systematics, the object SF systematics are propagated to all branches computed from the new object collections. By disabling the copy, this gets rid of spurious systematics branches + iterations in the systematics loop, as confirmed by @lesplend.

The configuration is thus updated to have the SF copy disabled. It has been found that the access to SF in downstream algorithms can be preserved by initialising the SysReadDecorHandle using the original container, instead of the view container.

FYI @aad @croland @mfujimot

Edited by Thomas Strebler

Merge request reports

Loading