-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: allow for not sorting during PATJetUpdater call #32297
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32297/20113
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
6663bc0
to
74b0314
Compare
74b0314
to
d5ab218
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32297/20116
|
A new Pull Request was created by @andrzejnovak (Andrzej Novak) for master. It involves the following packages: PhysicsTools/PatAlgos @perrotta, @jpata, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
-1 Tested at: d5ab218 CMSSW: CMSSW_11_3_X_2020-11-26-2300 I found follow errors while testing this PR Failed tests: HeaderConsistency ClangBuild
I found compilation error while trying to compile with clang. Command used:
>> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/RecoMETExtractor.cc >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/StringResolutionProviderESProducer.cc >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/TauJetCorrFactorsProducer.cc >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/TrackAndVertexUnpacker.cc >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/VertexAssociationProducer.cc /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/PATTriggerProducer.cc:45:21: error: call to implicitly-deleted default constructor of 'pat::PATTriggerProducer::ModuleLabelToPathAndFlags' PATTriggerProducer::PATTriggerProducer(const ParameterSet& iConfig) ^ /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_3_X_2020-11-26-2300/src/PhysicsTools/PatAlgos/plugins/PATTriggerProducer.h:145:39: note: default constructor of 'ModuleLabelToPathAndFlags' is implicitly deleted because field 'empty_' of const-qualified type 'const std::vector' would not be initialized const std::vector empty_; ^ |
Comparison not run due to Build errors/Fireworks only changes/No short matrix requested (RelVals and Igprof tests were also skipped) |
+1
|
assign xpog |
New categories assigned: xpog @fgolf,@mariadalfonso,@gouskos you have been requested to review this Pull request/Issue and eventually sign? Thanks |
+1 |
kind reminder @cms-sw/xpog-l2 |
I suppose this is not a critical PR to have in asap, but at the same time the change is trivial. |
I'm trying to figure out the case when you need to switch on/off this sorting. in the default nano in 10_6 PATJetUpdater is called 6 times. process.patJetsReapplyJEC = cms.EDProducer("PATJetUpdater", |
@mariadalfonso No, at the moment this is not needed for any central workflow, but if we wanted to re-calculate btags also for subjets like it currently does for fatjets, it would get used (pt sorting the subjets would mess up the subject link to |
If I can add something here, in the case when we were trying to run the AK8 jet collection with the new PUPPI tune from miniAOD, we would need to include this small fix as part of that PR to correctly handle the link between the subjet collection and the jet collection. |
Hi @alefisico Maria |
@mariadalfonso I am not sure what you mean. The only way you can detect something wrong has happened in this case is if you try to access the subjet collection and expect a specific ordering. i.e when the subjet index is explicitly used somewhere else like the linking to FatJets. I am not sure, but I think that's currently beyond the scope of the nano dqm. In the current CMSSW, calling
and therefore the values in [2] will point to different jets than intended. The effect is visible if one calculates the IIUC [1] is called in MINI production and not called again in Nano so the stored subjet collection is not pT ordered in neither MINI nor Nano. However, if it was needed to update the subjet collection in nano, like it is for regular jets [3] this would sort the subjet collection, scrambling the values in [2]. [1] https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/PatAlgos/python/slimming/applySubstructure_cff.py#L156-L194 |
kind reminder @cms-sw/xpog-l2 |
+xpog update the PATJetUpdater in view of future use of subject, see offline validation here |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Allow for running
updateJetCollection
without resorting the jets. This is to be used when i.e. updating subjet btag discriminators, but they are already ordered/matched to FatJets.Does not modify the default behaviour.
@alefisico