Added updateJetCollection() function to jetTools.py and related changes to the PATJetUpdater and the pat::Jet class

[ferencek]

This PR builds on top of #8288 and adds the updateJetCollection() function to jetTools.py. This function allows, in a user-friendly way, to update the jet energy corrections and re-run existing or add additional b-tag discriminators. It can also be used to add TagInfos to jets. It primarily targets updating pat::Jets stored in MiniAOD. In addition, users can manually add an arbitrary set of additional userFloats.

An example cfg file PhysicsTools/PatAlgos/test/patTuple_updateJets_fromMiniAOD_cfg.py was also added and included in PAT unit tests.

One caveat concerns added TagInfos. They cannot be successfully retrieved from pat::Jets stored in the existing MiniAOD datasets due to a bug in the PATJetSlimmer which was not clearing the tagInfoLabels_ data member of the pat::Jet class when dropping the TagInfos from slimmed jets. This PR therefore also includes a required bugfix for the PATJetSlimmer.

@ahinzmann @imarches @gpetruc @arizzi

[cmsbuild]

A new Pull Request was created by @ferencek (Dinko Ferenček) for CMSSW_8_0_X.

It involves the following packages:

DataFormats/PatCandidates
PhysicsTools/PatAlgos

@cvuosalo, @monttj, @cmsbuild, @slava77, @vadler, @davidlange6 can you please review it and eventually sign? Thanks.
@TaiSakuma, @imarches, @ahinzmann, @acaudron, @mmarionncern, @rappoccio, @jdolen, @nhanvtran, @schoef, @ferencek, @gpetruc, @mariadalfonso, @pvmulder this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

Following commands in first line of a comment are recognized

• +1|approve[d]|sign[ed]: L1/L2's to approve it
• -1|reject[ed]: L1/L2's to reject it
• assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
• unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
• hold: L1/all L2's/release manager to mark it as on hold
• unhold: L1/user who put this PR on hold
• merge: L1/release managers to merge this request
• [@cmsbuild,] please test: L1/L2 and selected users to start jenkins tests
• [@cmsbuild,] please test with cms-sw/cmsdist#<PR>: L1/L2 and selected users to start jenkins tests using externals from cmsdist

[slava77]

Is this renaming invisible to users (affects only transient objects)?
If it is not, why change the name?

[ferencek]

Yes, with the updateJetCollection() function from jetTools.py, this becomes a transient collection. Also, the new name is more in line with the PAT jet naming convention where user-defined labels and postfixes come after "PatJets" while "updated" is a fixed prefix-type descriptor.

[slava77]

@cmsbuild please test

@ferencek please update the PR subject line to be more descriptive of changes in the PATJetUpdater and pat::Jet

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10420/console

[cmsbuild]

+1
Tested at: b91cf04
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12863/10420/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12863/10420/summary.html

[ferencek]

@slava77, PR subject line updated

[slava77]

+1

for #12863 b91cf04

• code changes look OK. They affect only miniAOD part.
• jenkins tests pass and comparisons with the baseline show no differences in monitored quantities
• comparisons of miniAOD products (by branch size) show small differences in slimmedJetsPuppi and slimmedJets (changes are expected; no further checks are made to see specific variable changes in my checks)
• local test of miniAOD from AOD using pu35@25ns ttbar events show no significant change in CPU