NanoAOD: remove saveTriggerResults parameter from NanoAOD*OutputModule (revert #50057)#50797
NanoAOD: remove saveTriggerResults parameter from NanoAOD*OutputModule (revert #50057)#50797missirol wants to merge 2 commits intocms-sw:masterfrom
saveTriggerResults parameter from NanoAOD*OutputModule (revert #50057)#50797Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50797/49108
|
|
A new Pull Request was created by @missirol for master. It involves the following packages:
@battibass, @cmsbuild, @ftorrresd can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
enable nano |
|
please test |
|
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
Nano size comparison Summary:
NANO Comparison SummarySummary:
|
|
No warnings/errors, and no DQM differences (modulo #47071), in the outputs of the tests, as expected. |
|
+1 |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
PR description:
This PR reverts #50057 (which was integrated in
CMSSW_16_1_0_pre3).For what I understand (thanks to #50720), the parameter
saveTriggerResultsintroduced in #50057 is redundant, because settingsaveTriggerResultstoFalsein instances ofNanoAODOutputModuleis equivalent to "dropping" theedm::TriggerResultsproducts from those OutputModules.Merely technical, no changes expected in the outputs of PR tests.
Apologies for the back and forth!
PR validation:
Took
CMSSW_16_1_0_pre4(without this PR) and the step2 config of wf2500.3001(NanoAOD step), modified the latter config to useprocess.NANOAODSIMoutput.saveTriggerResults = cms.untracked.bool(False)in one case, andprocess.NANOAODSIMoutput.outputCommands += ["drop edmTriggerResults_*_*_*"]in another case,and verified that the NanoAOD outputs of (a) and (b) have the same branches (and no
edm::TriggerResults-related branches are present in the output files).If this PR is a backport, please specify the original PR and why you need to backport that PR. If this PR will be backported, please specify to which release cycle the backport is meant for:
No backports are necessary (if XPOG requests it, I can backport this PR to
16_1_Xin order to remove this redundant parameter in that cycle).