changes for data reco processing with 25ns

[slava77]

• to determine bunch spacing in data in PFClusterEMEnergyCorrector and EcalUncalibRecHitWorkerMultiFit
  • use run 253000 as a maximum with 50 ns if auto-selection is enabled
  • fixup/add manual bunch spacing setting is the auto-selection is disabled
• in RecoTLR (still using local customs implementation for run2 data processing)
  • remove CCC override-to-OFF in prompt and express customizations
  • add customise_DQM to the common customs (already in 75X/76X)
  • add customiseL1RecoForStage1 for stage1 unpackers and l1extra to use calo stage1
  • add customiseDataRun2Common_25ns (since I couldn't figure out how to more transparently set a default to 25ns and then be able to customize that to 50ns);
  • NB: the customiseDataRun2Common can still be used for Run2015B data processing as suggested in a few HN posts
  • add customiseDataRun2Common_50nsRunsAfter253000 function (it's in the name!) to force 50ns settings for runs after 253000, if we need it
  • remove outdated planBTracking
• add ppRun2at50ns scenario in T0 processing setup

tested in CMSSW_7_4_X_2015-08-01-1100
Configs for T0 tested

• with run_CfgTest.log
• by running ppRun2 and ppRun2at50ns with prompt reco (RunPromptReco.py) on /store/data/Run2015B/DoubleMuon/RAW/v1/000/251/721/00000/44C77595-412A-E511-930E-02163E012A2C.root.

Changes are as expected, appear only in the run2 T0 workflow:

• there are less tracks with less hits and the cluster charge on track shows a cutoff due to CCC (many plots downstream change as well consistent with CCC enabling)
  
  
• L1 plots changed quite a bit
  
  
  probably the only suspicious ones are based on HF: they are empty now
  
• no change is observed in running ppRun2at50ns and ppRun2 workflows on the run 251721 since the default bunch spacing detection in both cases falls to 50 ns setup.

In addition, tested the machinery with a run after 253000 /store/data/Run2015B/MinimumBias/RAW/v1/000/253/020/00000/BA19E72A-5B37-E511-B00F-02163E0134B5.root (the run is cosmics and has no tracker or muons included)
As expected,

• ppRun2at50ns and ppRun2 show differences in the ECAL hit energies (previously constrained to 0 values now yield some results, as expected from the change in the multifit configuration)
  
• the baseline and ppRun2at50ns in this case produce identical results in the reco products (there is no tracker in this run).
  • stage1 is not in this run and as a result, all related DQM plots are empty ... I'm assuming we will not be switching stage1 on and off once this all starts working next week @mulhearn @deguio @danduggan

[cmsbuild]

A new Pull Request was created by @slava77 (Slava Krutelyov) for CMSSW_7_4_X.

changes for data reco processing with 25ns

It involves the following packages:

Configuration/DataProcessing
RecoLocalCalo/EcalRecProducers
RecoParticleFlow/PFClusterProducer

@cmsbuild, @cvuosalo, @franzoni, @davidlange6, @slava77 can you please review it and eventually sign? Thanks.
@ghellwig, @mmarionncern, @argiro, @Martin-Grunewald, @lgray, @bachtis 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.

[slava77]

+1

for #10518 dc5da96

• based on the pre-PR submission tests
• jenkins tests pass and comparisons with the baseline show no differences

[rovere]

FYI.
@VinInn