use shunt factor in QIE11 hardcode calibrations

[kpedro88]

The QIE11 cards will be operated with a current shunt due to the high levels of charge generated by SiPMs. The starting value of the current shunt is expected to be a factor of 6. This will be reflected in the QIE calibrations, but had been left out of the simulated values until now.

This PR updates the hardcode conditions. A separate update to the database conditions will be made by @abdoulline et al.

[kpedro88]

@cmsbuild please test

[cmsbuild]

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

[cmsbuild]

A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_8_1_X.

It involves the following packages:

CalibCalorimetry/HcalPlugins

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

cms-bot commands are list here #13028

[cmsbuild]

+1
Tested at: 582ca79
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-16082/15507/summary.html

[cmsbuild]

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

[mmusich]

+1

[cmsbuild]

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

[davidlange6]

+1

[slava77]

@kpedro88
you mentioned that this is supposed to solve the high-energy hit issue.
jenkins shows no differences in 2017 workflows (including 2017HCALdev).

There are differences in 2023D3, apparently in HB part.
What's missing?

[kpedro88]

@slava77 this solves it in the hardcode conditions, which usually aren't applied in central workflows, except for phase2. @abdoulline is preparing the associated database condition update with these values, which will fix 2017.

[slava77]

ah, OK.
So, I wait for this then to check #15959

[abdoulline]

Kevin and Slava,

new HcalQIEData_2017_v2.0_mc has been submitted to appropriate 81X GT
queues and a request has been sent to AlCa yesterday. But it needs some
time to be propagated to GTs.

On Wed, 5 Oct 2016, Kevin Pedro wrote:

@slava77 this solves it in the hardcode conditions, which usually aren't applied in central workflows, except for
phase2. @abdoulline is preparing the associated database condition update with these values, which will fix 2017.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the
thread.[AEx02gQn0dzK7ygyPaqqLlz_TcdVVzI7ks5qwtlMgaJpZM4KNJXV.gif]

[mmusich]

@abdoulline see updated Global Tags at: #16101
This is to let people continue working on the development, everything will need to converge into a single scenario via #15994