Trk1B HLT menu

[perrotta]

After decision taken by TSG, the HLT Run2 menu is migrated to the "TK1B" tracking scenario.
At the same time, the "template-only" paths are removed from the GRun scenario.

[cmsbuild]

A new Pull Request was created by @perrotta for CMSSW_7_2_X.

Trk1B HLT menu

It involves the following packages:

Configuration/AlCa
FastSimulation/Tracking
HLTrigger/Configuration

@perrotta, @cmsbuild, @civanch, @diguida, @lveldere, @mdhildreth, @Martin-Grunewald, @nclopezo, @rcastello, @cerminar, @fwyzard can you please review it and eventually sign? Thanks.
@ghellwig 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.

[lveldere]

+1

[perrotta]

+1

[perrotta]

Thank you Salvatore!
Yes, as you see this is a temporary solution. But we need it merged in the CMSSW IB in order to continue integrating new paths in the HLT menu.
Ciao, A.

[diguida]

@perrotta
Operationally: For pre6 GTs (PR to be sent on Monday) I can include the Trk1B JEC in the HLT GT, and leave the other scenarios in autoCond, where the corresponding JEC override the labels in the GT.
I think this is a win-win situation: we have a consistent GT, you have the default in production.

[diguida]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine).

[cmsbuild]

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