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
Update global tags to include new EGamma regression #27089
Update global tags to include new EGamma regression #27089
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27089/10178
|
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 with #26892 |
The tests are being triggered in jenkins. |
-1 Tested at: 42bc42c You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following workflows: runTheMatrix-results/136.7611_RunJetHT2016E_reminiaod+RunJetHT2016E_reminiaod+REMINIAOD_data2016_HIPM+HARVESTDR2_REMINIAOD_data2016_HIPM/step2_RunJetHT2016E_reminiaod+RunJetHT2016E_reminiaod+REMINIAOD_data2016_HIPM+HARVESTDR2_REMINIAOD_data2016_HIPM.log136.8311 step2 runTheMatrix-results/136.8311_RunJetHT2017F_reminiaod+RunJetHT2017F_reminiaod+REMINIAOD_data2017+HARVEST2017_REMINIAOD_data2017/step2_RunJetHT2017F_reminiaod+RunJetHT2017F_reminiaod+REMINIAOD_data2017+HARVEST2017_REMINIAOD_data2017.log1325.7 step2 runTheMatrix-results/1325.7_TTbar_13_94Xv2NanoAODINPUT+TTbar_13_94Xv2NanoAODINPUT+NANOEDMMC2017_94XMiniAODv2+HARVESTNANOAODMC2017_94XMiniAODv2/step2_TTbar_13_94Xv2NanoAODINPUT+TTbar_13_94Xv2NanoAODINPUT+NANOEDMMC2017_94XMiniAODv2+HARVESTNANOAODMC2017_94XMiniAODv2.log |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
So our end goal is this:
I have to admit, I wasnt aware of the the single data GT originally but fine, its merely a technical detail. Now this simple picture is rather complicated by the fact that 2016, 2018 does not exist right now. And also you cant pre-prend iovs so at somepoint we'll need a new GT for data. This plan was agreed in PPD coordination. Get the conditions ready for 2017, get that running and then get 2018, then 2016, there being little point in waiting another month to start 2017. At this point, none of this is specific to e/gamma, and hopefully should not be news to anybody. Now on to E/gamma. For the PF cluster and mustache SC, they can share the same code so they are simply a conditions update. There was some confusion and they were orignally applied for all tags. But that should be reverted now. They should be no different to any other conditions prep for 2017. Now we get to the electron/photon regressions. These are not backwards compatible changes. This was made even more tedious by oversights in the original conf format which is just the payload of the GBRForest but not the meta data needed to interpret it, such as the response range and the variables used. Therefore we are in the lovely situation where the payload is controlled by the GT but the meta data is in the release. This normally wouldn't be a huge issue except for the fact in this unique situation we're sending out the release before finishing the conditions. In time, new conditions will be deployed for 2016, 2018 which will mean updating the release at that point in time as well. Its not as if the conditions they currently get are in any way right or correct btw. 2016/2018 are currently in an intermediate undefined and non-physics quality state. This is simply unavoidable and is a chicken and egg scenario (which I want to see if we can do something about in the future). Also in time, I'll probably update the default conditions as well to the new ele/pho regressions. Its not as if the regression RunI or HION currently gets is in anyway tuned to it, however it should probably have the conditions matched to its PF rec-hit thresholds which as far as I can tell is the 2018 PF rec-hit thresholds tuned on an overly pessimistic ecal noise model. |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 The sole purpose of this PR is to support PR #26892. Given the reco signature for that PR, I am signing off here. |
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) |
+1 |
PR description:
This PR adds test GTs needed to test PR #26892 and should be merged simultaneously with that PR. I created a separate PR so that I could launch the PR tests myself now but the two PRs could be merged if that's more convenient. The naming of the GTs will be fixed with the autoCond update that finalizes the 2017 UL data and MC GTs. The diffs of the changed GTs with respect to the current autoCond GTs are below:
106X_mcRun1_design_forPR26892_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun1_design_forPR26892_v1/106X_mcRun1_design_v1
106X_mcRun1_realistic_forPR26892_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun1_realistic_forPR26892_v1/106X_mcRun1_realistic_v1
106X_mcRun1_HeavyIon_forPR26892_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun1_HeavyIon_forPR26892_v1/106X_mcRun1_HeavyIon_v1
106X_mcRun1_pA_forPR26892_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun1_pA_forPR26892_v1/106X_mcRun1_pA_v1
106X_mcRun2_startup_forPR26892_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_startup_forPR26892_v2/106X_mcRun2_startup_v2
106X_mcRun2_asymptotic_l1stage1_forPR26892_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_asymptotic_l1stage1_forPR26892_v2/106X_mcRun2_asymptotic_l1stage1_v2
106X_mcRun2_design_forPR26892_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_design_forPR26892_v3/106X_mcRun2_design_v3
106X_mcRun2_asymptotic_forPR26892_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_asymptotic_forPR26892_v3/106X_mcRun2_asymptotic_v3
106X_mcRun2_HeavyIon_forPR26892_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_HeavyIon_forPR26892_v2/106X_mcRun2_HeavyIon_v2
106X_mcRun2_pA_forPR26892_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun2_pA_forPR26892_v2/106X_mcRun2_pA_v2
106X_dataRun2_forPR26892_v11
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun2_forPR26892_v11/106X_dataRun2_v11
106X_dataRun2_relval_forPR26892_v10
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun2_relval_forPR26892_v10/106X_dataRun2_relval_v10
106X_dataRun2_PromptLike_HEfail_forPR26892_v6
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun2_PromptLike_HEfail_forPR26892_v6/106X_dataRun2_PromptLike_HEfail_v6
106X_dataRun2_PromptLike_forPR26892_v7
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun2_PromptLike_forPR26892_v7/106X_dataRun2_PromptLike_v7
106X_dataRun2_PromptLike_HI_forPR26892_v7
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_dataRun2_PromptLike_HI_forPR26892_v7/106X_dataRun2_PromptLike_HI_v7
106X_mc2017_design_IdealBS_forPR26892_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mc2017_design_IdealBS_forPR26892_v4/106X_mc2017_design_IdealBS_v4
106X_mc2017_realistic_forPR26892_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mc2017_realistic_forPR26892_v3/106X_mc2017_realistic_v3
106X_upgrade2018_design_forPR26892_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2018_design_forPR26892_v3/106X_upgrade2018_design_v3
106X_upgrade2018_realistic_forPR26892_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2018_realistic_forPR26892_v4/106X_upgrade2018_realistic_v4
106X_upgrade2018_realistic_HI_forPR26892_v2
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2018_realistic_HI_forPR26892_v2/106X_upgrade2018_realistic_HI_v2
106X_upgrade2018_realistic_HEfail_forPR26892_v4
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2018_realistic_HEfail_forPR26892_v4/106X_upgrade2018_realistic_HEfail_v4
106X_upgrade2021_design_forPR26892_v1
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_design_forPR26892_v1/106X_upgrade2021_design_v1
106X_upgrade2021_realistic_forPR26892_v5
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_forPR26892_v5/106X_upgrade2021_realistic_v5
106X_upgrade2023_realistic_forPR26892_v3
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2023_realistic_forPR26892_v3/106X_upgrade2023_realistic_v3
PR validation:
Tested with PR #26892 on workflow 27434.0.
if this PR is a backport please specify the original PR:
This PR will need to be backported to 10_6_X.