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
GTs updated with Tracking, SiStripDQM Trigger Keys, HCAL electronics map, ZeroMaterial Geom #18136
GTs updated with Tracking, SiStripDQM Trigger Keys, HCAL electronics map, ZeroMaterial Geom #18136
Conversation
A new Pull Request was created by @arunhep (Arun Kumar) for master. It involves the following packages: Configuration/AlCa @ghellwig, @arunhep, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
@fioriNTU FYI |
@makortel FYI As tracking has been updated in this PR so we see slight increase in tracking efficiency from Sim to RECO https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_9_1_X_2017-03-30-1100+18136/19110/10024.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/Tracking_Track_cutsRecoHp_trackingParticleRecoAsssociation.html @mmusich is this expected? https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_9_1_X_2017-03-30-1100+18136/19110/4.53_RunPhoton2012B+RunPhoton2012B+HLTD+RECODR1reHLT+HARVESTDR1reHLT/AlCaReco.html |
@slava77 @perrotta This PR contains the updated phase1 initialStep MVA selection. Here are MTV plots for expected changes
For the record this update was presented in RECO meeting March 24 |
I'm not really sure why the improvement does not show up in PR tests, maybe it (and the original efficiency drop in HP) is visible only with pileup? (I just re-tested in 900 and the tag from CondDB that the improvement is there in ttbar+35PU) |
No. It is not expected. On the other hand the conditions are instead exactly what one expects. For instance the Global Tag used in the and if I compare the payloads for
resulting in: --- triggerBitsAlCaRecoTriggerBits_TrackerDQM_v5_offline.twiki 2017-03-31 11:47:00.529893225 +0200
+++ triggerBitsAlCaRecoTriggerBits_TrackerDQM_v6_offline.twiki 2017-03-31 11:44:49.853437522 +0200
@@ -1,6 +1,7 @@
---+++++ *IOV*: 1-264291
| *TriggerBits list key* | *HLT paths* |
-| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
+| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*', 'HLT_L1SingleMuOpen_v*', 'HLT_PAL1MinimumBiasHF_OR_SinglePixelTrack_*' |
+| 'SiStrip_IB_HLT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_*', 'HLT_ZeroBias_IsolatedBunches_v*' |
| 'SiStrip_L1' | 'L1_ZeroBias' |
| 'Tracking_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
| 'Tracking_HLT_HIP_OOT' | 'HLT_ZeroBias_FirstBXAfterTrain_v*' |
@@ -8,7 +9,8 @@
| 'Tracking_HLT_noHIP_noOOT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_v*' |
---+++++ *IOV*: 264292-284024
| *TriggerBits list key* | *HLT paths* |
-| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
+| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*', 'HLT_L1SingleMuOpen_v*', 'HLT_PAL1MinimumBiasHF_OR_SinglePixelTrack_*' |
+| 'SiStrip_IB_HLT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_*', 'HLT_ZeroBias_IsolatedBunches_v*' |
| 'SiStrip_L1' | 'L1Tech_BPTX_plus_AND_minus.v0', 'L1_ZeroBias', 'L1_ExtCond_032' |
| 'Tracking_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*' |
| 'Tracking_HLT_HIP_OOT' | 'HLT_ZeroBias_FirstBXAfterTrain_v*' |
@@ -16,7 +18,8 @@
| 'Tracking_HLT_noHIP_noOOT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_v*' |
---+++++ *IOV*: 284025-500000
| *TriggerBits list key* | *HLT paths* |
-| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*', 'HLT_L1SingleMuOpen_v*', 'HLT_ZeroBias_FirstCollisionAfterAbortGap_*', 'HLT_ZeroBias_IsolatedBunches_v*', 'HLT_PAL1MinimumBiasHF_OR_SinglePixelTrack_*' |
+| 'SiStrip_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*', 'HLT_L1SingleMuOpen_v*', 'HLT_PAL1MinimumBiasHF_OR_SinglePixelTrack_*' |
+| 'SiStrip_IB_HLT' | 'HLT_ZeroBias_FirstCollisionAfterAbortGap_*', 'HLT_ZeroBias_IsolatedBunches_v*' |
| 'SiStrip_L1' | 'L1Tech_BPTX_plus_AND_minus.v0', 'L1_ZeroBias', 'L1_ExtCond_032', 'L1_MinimumBiasHF0_OR_BptxAND*' |
| 'Tracking_HLT' | 'HLT_ZeroBias_v*', 'HLT_HIZeroBias_v*', 'HLT_BptxAnd_*', 'HLT_PAL1MinimumBiasHF_OR_SinglePixelTrack_*' |
| 'Tracking_HLT_HIP_OOT' | 'HLT_ZeroBias_FirstBXAfterTrain_v*' | change in conditions for the IOV for 2012B (the run probed in wf 4.53 is 194533 which falls in the IOV 1-264291) is the same as for the IOV for 2016B (wf 136.731 uses run 274199 which falls in IOV 264292-284024). On the other hand as you pointed out there are differences in 4.53 I am wondering if it is related with the reproducibility issue (to my knowledge not yet solved) detailed in https://its.cern.ch/jira/browse/CMSTRACK-151 (@fioriNTU, @mtosi) |
We've had instability in that folder of plots in all pull requests I've scrutinized this year, irrespective of whether changes effected alcarecos or not. |
please test |
The tests are being triggered in jenkins. |
Description updated with the latest commit for including L1 Prescale and Vetoes for MC. |
Comparison job queued. |
+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 requires discussion in the ORP meeting before it's merged. @Muzaffar, @davidlange6, @smuzaffar |
@rekovic FYI |
+1 |
Summary of changes in Global Tags
RunI simulation
RunI Heavy Ions scenario : 91X_mcRun1_HeavyIon_v1 as 90X_mcRun1_HeavyIon_v4 with the following changes:
RunI Ideal scenario : 91X_mcRun1_design_v1 as 90X_mcRun1_design_v4 with the following changes:
RunI Proton-Lead scenario : 91X_mcRun1_pA_v1 as 90X_mcRun1_pA_v4 with the following changes:
RunI Realistic scenario : 91X_mcRun1_realistic_v1 as 90X_mcRun1_realistic_v4 with the following changes:
RunII simulation
RunII Asymptotic scenario : 91X_mcRun2_asymptotic_v2 as 90X_mcRun2_asymptotic_v5 with the following changes:
RunII CRAFT scenario : 91X_mcRun2cosmics_startup_deco_v2 as 90X_mcRun2cosmics_startup_deco_v1 with the following changes:
RunII Heavy Ions scenario : 91X_mcRun2_HeavyIon_v2 as 90X_mcRun2_HeavyIon_v4 with the following changes:
RunII Ideal scenario : 91X_mcRun2_design_v2 as 90X_mcRun2_design_v5 with the following changes:
RunII Proton-Lead scenario : 91X_mcRun2_pA_v2 as 90X_mcRun2_pA_v5 with the following changes:
RunII Startup scenario : 91X_mcRun2_startup_v2 as 90X_mcRun2_startup_v4 with the following changes:
RunI data
RunI HLT processing : 91X_dataRun2_HLT_frozen_v1 as 90X_dataRun2_HLT_frozen_v4 with the following changes:
RunI Offline processing : 91X_dataRun2_v1 as 90X_dataRun2_v6 with the following changes:
RunII data
RunII HLTHI processing : 91X_dataRun2_HLTHI_frozen_v1 as 90X_dataRun2_HLTHI_frozen_v4 with the following changes:
RunII HLT processing : 91X_dataRun2_HLT_frozen_v1 as 90X_dataRun2_HLT_frozen_v4 with the following changes:
RunII HLT relval processing : 91X_dataRun2_HLT_relval_v1 as 90X_dataRun2_HLT_relval_v4 with the following changes:
RunII Offline processing : 91X_dataRun2_v1 as 90X_dataRun2_v6 with the following changes:
RunII Offline relval processing : 91X_dataRun2_relval_v1 as 90X_dataRun2_relval_v6 with the following changes:
RunII Prompt processing : 91X_dataRun2_PromptLike_v1 as 90X_dataRun2_PromptLike_v6 with the following changes:
Upgrade
PhaseII realistic scenario : 91X_upgrade2023_realistic_v1 as 90X_upgrade2023_realistic_v9 with the following changes:
PhaseI 2017 cosmics peak scenario : 91X_upgrade2017cosmics_realistic_peak_v2 as 90X_upgrade2017cosmics_realistic_peak_v19 with the following changes:
PhaseI 2017 cosmics scenario : 91X_upgrade2017cosmics_realistic_deco_v2 as 90X_upgrade2017cosmics_realistic_deco_v18 with the following changes:
PhaseI 2017 design scenario : 91X_upgrade2017_design_IdealBS_v2 as 90X_upgrade2017_design_IdealBS_v19 with the following changes:
PhaseI 2017 realistic scenario : 91X_upgrade2017_realistic_v2 as 90X_upgrade2017_realistic_v20 with the following changes:
PhaseI 2018 cosmics scenario : 91X_upgrade2018cosmics_realistic_deco_v2 as 90X_upgrade2018cosmics_realistic_deco_v17 with the following changes:
PhaseI 2018 design scenario : 91X_upgrade2018_design_IdealBS_v2 as 90X_upgrade2018_design_IdealBS_v15 with the following changes:
PhaseI 2018 realistic scenario : 91X_upgrade2018_realistic_v2 as 90X_upgrade2018_realistic_v17 with the following changes: