Disabling the reclustering in the MET correction and uncertainty tool

[mmarionncern]

Following the discussion of https://indico.cern.ch/event/447792/?filterActive=1&showDate=all&showSession=4
this PR removes the jet clustering and enable the repro74X option in the shortcut functions used for MET reprocessing on top of miniAOD.

New features :

• MET extractor : allows to retrieve the raw MET from an existing slimmedMET collection; the recomputation of the raw MET is thus not needed anymore if not explicitely specified in the tool
• jet reclustering disabled per default, existing slimmedJets are directly recalibrated using the last JECs and the Type1MET is defined accordingly
• the repro74X option has been added in the runMetCorAndUncFromMiniAOD function, allowing users to recompute the MET on top of 74X, X<12 miniAODs on the fly in a simplified way.
• the caloMET is now copied in the new slimmedMET collection
• automatic protection has been added against the change of process name used to create the first slimmed MET collection. Users won't have to switch manually the input tag to slimmedMET__RECO anymore

Changes expected :

• gain of CPU performances
• physics untouched, rounding of PFcandidate quantities removed from the computations.

Has to be done on top of #11482

[cmsbuild]

A new Pull Request was created by @mmarionncern for CMSSW_7_4_X.

Disabling the reclustering in the MET correction and uncertainty tool

It involves the following packages:

JetMETCorrections/Type1MET
PhysicsTools/PatAlgos
PhysicsTools/PatUtils

@cmsbuild, @vadler, @monttj can you please review it and eventually sign? Thanks.
@rappoccio, @imarches, @ahinzmann, @acaudron, @TaiSakuma, @jdolen, @nhanvtran, @schoef, @ferencek, @gpetruc, @mariadalfonso, @pvmulder this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[slava77]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.

[gpetruc]

Hi @mmarionncern,

This PR affects only the re-computation of type1 MET from miniAOD, not what's run in prooduction, ok?

Giovanni

[mmarionncern]

@gpetruc Yes, the type1MET correction is only computed at the miniAOD level so far.

[gpetruc]

Naive question: shouldn't there be also L2L3Residual?

[mmarionncern]

There is a specific case for data L1252 of the new version

[cmsbuild]

+1
Tested at: 11b0065
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11489/8392/summary.html

[cmsbuild]

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

The workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons