-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Backport of Muon L1 prefire weights #33759
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
Changes from all commits
f475bcb
3db916c
4f60410
50f940b
2fac91c
447aafc
d752ac6
97c3c7c
67afdb9
de785c4
34fdaef
c7471ec
fd55306
3c05ba7
16ca043
9a4afae
5a0e55d
6267072
c848b76
991fa3b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -554,11 +554,11 @@ def miniAOD_customizeCommon(process): | |
|
|
||
| # L1 pre-firing weights for 2016 and 2017 | ||
| from Configuration.Eras.Modifier_run2_L1prefiring_cff import run2_L1prefiring | ||
| from Configuration.Eras.Modifier_stage1L1Trigger_cff import stage1L1Trigger | ||
| from Configuration.Eras.Modifier_stage2L1Trigger_cff import stage2L1Trigger | ||
| from Configuration.Eras.Modifier_stage2L1Trigger_2017_cff import stage2L1Trigger_2017 | ||
| process.load("PhysicsTools.PatUtils.L1ECALPrefiringWeightProducer_cff") | ||
| stage1L1Trigger.toModify(process.prefiringweight, DataEra = "2016BtoH") | ||
| stage2L1Trigger_2017.toModify(process.prefiringweight, DataEra = "2017BtoF") | ||
| process.load("PhysicsTools.PatUtils.L1PrefiringWeightProducer_cff") | ||
| stage2L1Trigger.toModify(process.prefiringweight, DataEraECAL = "2017BtoF", JetMaxMuonFraction = -1, DoMuons = cms.bool(False) ) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the era correct here ("2017BtoF")?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if we want to reproduce the configuration previous to this PR to comply with the rule forbidding changes to RECO, yes. (these 2017 maps were also mistakenly picked previously for 2016 ...)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Ok, thank you! |
||
| stage2L1Trigger_2017.toModify(process.prefiringweight, DataEraECAL = "2017BtoF", JetMaxMuonFraction = -1, DoMuons = cms.bool(False)) | ||
|
Comment on lines
-559
to
+561
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this suppose to lead to any changes in the production miniAOD (especially UL)?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, this is specifically set to prevent any changes to miniAOD by deactivating the new features and using the pre-UL ECAL maps.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we need to have something set for the stage2L1Trigger_2018?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the same rule of not changing the miniAOD output applies here, not thing was set for 2018 before, so we set nothing now. |
||
| run2_L1prefiring.toModify(task, func=lambda t: t.add(process.prefiringweight)) | ||
|
|
||
| def miniAOD_customizeMC(process): | ||
|
|
||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mariadalfonso Here we remove the new prefiring weights from the nano event content for V8, so having empty histograms for them in DQM is expected. What I am a puzzled about is why the prefiring weight is 1, it should still reflect the ECAL prefiring. What workflow did you use for that test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mhhh, now that we have the UL maps for ECAL, this might need a further protection for that year. @lathomas