-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
add onlineBeamSpotESProducer to BeamSpot_cfi: fix general Online BS swap case #35639
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35639/25912
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @slava77, @jpata, @tvami, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -4,6 +4,11 @@ | |||
|
|||
offlineBeamSpot = cms.EDProducer("BeamSpotProducer") | |||
|
|||
import RecoVertex.BeamSpotProducer.onlineBeamSpotESProducer_cfi as _mod | |||
BeamSpotESProducer = _mod.onlineBeamSpotESProducer.clone( | |||
timeThreshold = 999999 # for express allow >48h old payloads for replays. DO NOT CHANGE |
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.
Does this mean that wherever this module is imported it gets this timeThreshold
? I don't think this is the intended use for the HLT case, right @gennai ?
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.
Isn't HLT fully dumped anyway?
please test |
I am not even sure it would work for importing the beamspotProducer in the menu. I do not know if confDB can ignore the part not related to the module description, @Sam-Harper may know better than I do. |
or even @Martin-Grunewald may know the answer |
What is the actual question? The beam spot producer currently in 12_1 HLT offline/development menus is the
There is no parameter called |
Indeed it is:
and that's what we want for HLT, no? @gennai @francescobrivio |
Perhaps you talk about CRUZET/CRAFT menus by FOG? |
If you want to replace the In ConfDB the following is available for use:
Changing the |
Correct, 48h is what we want! |
Thanks @Martin-Grunewald that's perfect! We do not want to change any of those parameters in the HLT, so the configuration from ConfDB that you reported is the correct one to be used. |
Sorry everybody I was unclear. The ESProducer is already in the menu as well as the OnlineBeamSpotProducer with the proper configuration and we do not want to change it. I was referring to the fact that the proposal fix is adding few lines to a cfi file adding on top of the OnlineBeamSpotProducer configuration also an import of the ESProducer module with a change in one parameter. I was questioning (mostly @Martin-Grunewald) if the practice of adding other modules in a cfi file could have given issues in future migration of the DB templates to later releases. IF it is not the case I am fine with the fix. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-30d3c1/19583/summary.html Comparison SummarySummary:
|
test parameters:
|
@cmsbuild please test |
urgent |
+reconstruction for #35639 d6091aa
|
+alca |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
merge |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-30d3c1/19656/summary.html Comparison SummarySummary:
|
resolves #35634
PR description:
In PR #35373 the general case for the online <-> offline BS swap done via modifiers was missed, leading to issues in the visualization DQM clients.
This PR supplies the
onlineBeamSpotESProducer
toBeamSpot_cfi
as a general case fix-up.PR validation:
Run
cmsRun DQM/Integration/python/clients/visualization-live_cfg.py unitTest=True
that before was crashing with:
while now crashes differently with:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Not a backport, but should be backported.