[10.0.X] Update GT: Update all L1T tags #21137
Conversation
|
The code-checks are being triggered in jenkins. |
|
please test |
|
+code-checks |
|
The tests are being triggered in jenkins. |
|
A new Pull Request was created by @lpernie (Luca Pernie) for master. It involves the following packages: Configuration/AlCa @ghellwig, @arunhep, @cerminar, @cmsbuild, @rekovic, @franzoni, @mulhearn, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cmsbuild
added
code-checks-pending
tests-pending
and removed
code-checks-approved
tests-started
labels
|
The code-checks are being triggered in jenkins. |
|
please test |
|
+code-checks |
|
The tests are being triggered in jenkins. |
|
@jfernan2 Thanks ! |
|
please test |
cmsbuild
added
comparison-pending
tests-pending
and removed
comparison-available
tests-approved
labels
|
The tests are being triggered in jenkins. |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
Comparison is ready Comparison Summary:
|
|
@davidlange6 can this PR be merged please? With this we will have this duplicity removed for L1T fake EMTF params and we can arrange the queues accordingly. Thanks. |
|
@davidlange6 can this PR be merged please? |
|
i didn't have a chance to understand the physics changes on Friday. Do you expect them? |
|
@davidlange6 we don't expect physics changes because of these updates. And i don't see any in 2017, 2018 MC. can you please point me to the changes which you may have seen and not directly understood from these updates? |
|
Perhaps, @rekovic can give a better summary of the DQM differences, but as far as I remember, for the L1T, DQM results for data are expected to be different between new and old GTs. We've finally switched to configuring L1T from O2O tags in CondDB as opposed to static pythons as it was before. |
|
instead of the nominal 1 histogram changed there are ~2000 - I didn't look further yet
… On Nov 20, 2017, at 10:45 AM, Arun Kumar ***@***.***> wrote:
@davidlange6 we don't expect physics changes because of these updates.
these updates are mainly for L1T caloParams and BMTF and EMTF parameters.
And i don't see any in 2017, 2018 MC.
for data wf 136.731 I see only changes in the L1T directory : https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_10_0_X_2017-11-15-1100+21137/23739/136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2/L1T.html
can you please point me to the changes which you may have seen and not directly understood from these updates?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
looks like 2017B data, 2016B data |
|
When we introduced the NoHackConditions originally we knew that we were missing some BMTF Conditions from the GT. #20871 (comment) Now, this PR provides the missing BMTF conditions, and we now have ~2000 histograms showing differences. The numbers make sense. Need to look at the histograms. |
|
All the differences I found have to do with uGMT (i.e. Muons), fund in either An example being data vs emul comparisons in Another example is change in As usual, we need to look at the higher statistics RelVal samples to finally validate the new release. +1 |
|
merge |
Summary of changes in Global Tags
RunI data
RunI HLT processing : 94X_dataRun2_HLT_frozen_v3 as 94X_dataRun2_HLT_frozen_v4 with the following changes:
RunI Offline processing : 94X_dataRun2_v2 as 94X_dataRun2_v3 with the following changes:
RunII data
RunII HLTHI processing : 94X_dataRun2_HLTHI_frozen_v2 as 94X_dataRun2_HLTHI_frozen_v3 with the following changes:
RunII HLT relval processing : 94X_dataRun2_HLT_relval_v5 as 94X_dataRun2_HLT_relval_v6 with the following changes:
RunII Offline processing : 94X_dataRun2_v2 as 94X_dataRun2_v3 with the following changes:
RunII Offline relval processing : 94X_dataRun2_relval_v5 as 94X_dataRun2_relval_v6 with the following changes:
RunII Prompt processing : 94X_dataRun2_PromptLike_v5 as 94X_dataRun2_PromptLike_v6 with the following changes:
RunI HLT processing : 94X_dataRun2_HLT_frozen_v3 as 94X_dataRun2_HLT_frozen_v4 with the following changes:
Upgrade
PhaseII realistic scenario : 94X_upgrade2023_realistic_v2 as 94X_upgrade2023_realistic_v3 with the following changes:
PhaseI 2018 cosmics scenario : 94X_upgrade2018cosmics_realistic_deco_v4 as 94X_upgrade2018cosmics_realistic_deco_v5 with the following changes:
PhaseI 2018 design scenario : 94X_upgrade2018_design_IdealBS_v5 as 94X_upgrade2018_design_IdealBS_v6 with the following changes:
PhaseI 2018 realistic scenario : 94X_upgrade2018_realistic_v5 as 94X_upgrade2018_realistic_v6 with the following changes:
2017_MC
PhaseI 2017 cosmics peak scenario : 94X_mc2017cosmics_realistic_peak_v4 as 94X_mc2017cosmics_realistic_peak_v5 with the following changes:
PhaseI 2017 cosmics scenario : 94X_mc2017cosmics_realistic_deco_v4 as 94X_mc2017cosmics_realistic_deco_v5 with the following changes:
PhaseI 2017 design scenario : 94X_mc2017_design_IdealBS_v5 as 94X_mc2017_design_IdealBS_v6 with the following changes:
PhaseI 2017 realistic scenario : 94X_mc2017_realistic_v5 as 94X_mc2017_realistic_v6 with the following changes: