Re-add eventSetupPathKey to ALCARECOLumiPixels

[mmusich]

This PR allows the possibility to steer the selection of the trigger bits populating the ALCARECOLumiPixels ALCARECO via TriggerBit stored in DB.

This should solve the issue with the problematic version of the trigger:
AlCa_PAL1MinimumBiasHF_OR_SinglePixelTrack_v1
creating events with event content not manageable by the ALCARECOLumiPixels reported in: HN link by filtering out the offending trigger with an appropriate DB payload.

Tested working via:

cmsrel CMSSW_8_0_24
cd CMSSW_8_0_24/src
git cms-init
git remote add cms-AlCaDB git@github.com:cms-AlCaDB/cmssw.git
git fetch cms-AlCaDB
git checkout 80X_addSetupPathKeyLumiPixels
git cms-addpkg Calibration/TkAlCaRecoProducers
git cms-addpkg Configuration/DataProcessing
scramv1 b -j 8
cd Configuration/DataProcessing/test/
python RunPromptReco.py --scenario AlCaLumiPixels --global-tag 80X_dataRun2_Prompt_v15 --lfn /store/hidata/PARun2016B/AlCaLumiPixels/RAW/v1/000/285/368/00000/7EC99302-E2AC-E611-A135-02163E01465B.root --reco --dqmio --alcarecos=LumiPixels
cmsRun RunPromptReco.py

attn: @trtomei @tocheng @capalmer85

[mmusich]

please test

[cmsbuild]

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

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_8_0_X.

It involves the following packages:

Calibration/TkAlCaRecoProducers

@ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @threus, @tocheng this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

[capalmer85]

@mmusich For pp running next year (2017), we do NOT want to use this trigger. Will we simply have it set to 0 all the time or will this be in a separate "branch" specific for HI development?

[mmusich]

@capalmer85

we do NOT want to use this trigger. Will we simply have it set to 0 all the time or will this be in a separate "branch" specific for HI development

that's exactly what triggerbits in DB are meant for. Currently you were accepting everything in the PD...

[cmsbuild]

+1
Tested at: a67d039
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16684/16470/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
7d7f3e0
c6e3ab9
03f01e7
395c063
14e4116
5076dd9
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16684/16470/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16684/16470/git-merge-result

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

[cmsbuild]

Pull request #16684 was updated. @ghellwig, @arunhep, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please check and sign again.

[mmusich]

please test

[cmsbuild]

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

[cmsbuild]

+1
Tested at: 1e5c156
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16684/16507/summary.html

[cmsbuild]

Comparison job queued.

[mmusich]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar

[cmsbuild]

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

[davidlange6]

+1