New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrected 5 channels of 2016 ECAL intercalibration #29023
Corrected 5 channels of 2016 ECAL intercalibration #29023
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29023/13873
|
A new Pull Request was created by @christopheralanwest for master. It involves the following packages: Configuration/AlCa @christopheralanwest, @tocheng, @cmsbuild, @franzoni, @tlampen, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
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, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR corrects five channels of the 2016 ECAL intercalibration that JetMET identified as problematic during the 2016 UL validation. Only the offline data GTs are updated, with only a single tag update, as seen in the GT diffs below:
Offline data
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/111X_dataRun2_v1/111X_dataRun2_v2
Offline data with emulation of HEM failure
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/111X_dataRun2_HEfail_v1/111X_dataRun2_HEfail_v2
Offline data relval
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/111X_dataRun2_relval_v1/111X_dataRun2_relval_v2
PR validation:
See the presentation at the 10 Feb 2020 AlCaDB meeting and the 20 Feb 2020 PPD meeting for details of the validation.
if this PR is a backport please specify the original PR and why you need to backport that PR:
This PR is not a backport but it will be backported to 10_6_X for use in the UL reprocessing. For consistency, the bug fix will also be propagated to 11_0_X.