[10.4.X] add missing eventSetupPathsKey swap for HI 2018

[mmusich]

Greetings,
as the HLT_HIZeroBias_FirstCollisionAfterAbortGap_v* trigger has been confirmed for the HI HLT menu for 2018 PbPb data-taking, it would be good to use the HI trigger bit eventSetupPathsKey. This is part of the same campaign of adjusting the pp ALCARECO for the pp_on_AA era: #24596.
Once merged, an update of the Express GT will be needed as at the moment the key SiStripCalMinBiasAAGHI is not available.

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24975/6946

[cmsbuild]

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

It involves the following packages:

Calibration/TkAlCaRecoProducers

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

cms-bot commands are listed here

[tocheng]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/31230/console Started: 2018/10/23 15:39

[cmsbuild]

+1
Tested at: 503e701
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-24975/31230/summary.html

[cmsbuild]

Comparison job queued.

[tocheng]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 32
• DQMHistoTests: Total histograms compared: 2994843
• DQMHistoTests: Total failures: 1
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2994645
• DQMHistoTests: Total skipped: 197
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
• Checked 134 log files, 14 edm output root files, 32 DQM output files

[fabiocos]

@mmusich your comment means that a backport of this PR should be linked to a corresponding update of a GT, otherwise it will break the release, am I correct?

[mmusich]

@fabiocos technically it won't break the relvals as this AlCaReco is not excercised yet in this mode (i.e. using the pp_on_AA_2018 era) in any workflow, but if the backport is merged indeed before running this at tier-0 an update of the express GT is needed.

[mmusich]

Just to be clear, when I say update I just mean an append IOV, the GT doesn't need to be necessarily changed.

[fabiocos]

@mmusich ok thank
@lpernie @tocheng what is the plan for such an update?

[fabiocos]

+1

[tocheng]

@mmusich ok thank
@lpernie @tocheng what is the plan for such an update?

@fabiocos No later than next CMSSW_10_3_X release where merge of #24976 is merged
We are going to append a new IOV to the current trigger selection to include all the changes needed for heavy Ion data taking.