-
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
added the possibility to lock a record #33659
added the possibility to lock a record #33659
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33659/22551
|
A new Pull Request was created by @gennai (simone gennai) for master. It involves the following packages: DQM/BeamMonitor @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: Build Python3 BuildI found compilation warning when building: See details on the summary page. #Python3 I found errors: *** Error compiling 'src/DQM/Integration/python/clients/beam_dqm_sourceclient-live_cfg.py'... |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33659/22557
|
Pull request #33659 was updated. @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please check and sign again. |
@jfernan2 could you trigger the test, or is there anything else I should do for the warnings? |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f6f4b1/14974/summary.html Comparison SummarySummary:
|
@gennai since this PR is affecting Online DQM mainly, could you make a 11_3_X PR version to test it at P5 machines? Next MWGR is planning to use 11_3_X, unless you don't plan to use it by then |
I am already working on it, I was waiting this PR to be scrutinized to apply the same comments to the back porting |
Backporting is #33684 Best, |
Thank you! @gennai |
+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 will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
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.
I would also suggest (not related to this PR) to use clone
process.dqmBeamMonitor = process.dqmFakeBeamMonitor.clone(
OnlineMode = True,
useLockRecords = useLockRecords,
[...]
)
instead of
process.dqmBeamMonitor = process.dqmFakeBeamMonitor.clone()
process.dqmBeamMonitor.useLockRecords = useLockRecords
process.dqmBeamMonitor.OnlineMode = True
[...]
in the first case the mis-spelled variable name would give error. See for instance https://github.com/cms-sw/cmssw/pull/33046/files
and
When one customizes an existing parameter in clone(), Modifier.toModify(), or in assignment, explicit types on the right hand side should be avoided.
in https://cms-sw.github.io/cms_coding_rules.html
@@ -137,6 +137,7 @@ BeamMonitor::BeamMonitor(const ParameterSet& ps) | |||
minNrVertices_ = ps.getParameter<ParameterSet>("PVFitter").getUntrackedParameter<unsigned int>("minNrVerticesForFit"); | |||
minVtxNdf_ = ps.getParameter<ParameterSet>("PVFitter").getUntrackedParameter<double>("minVertexNdf"); | |||
minVtxWgt_ = ps.getParameter<ParameterSet>("PVFitter").getUntrackedParameter<double>("minVertexMeanWeight"); | |||
useLockRecords_ = ps.getUntrackedParameter<bool>("useLockRecords"); |
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 better to have it as a tracked parameter? (same comment for other parameters above, not related to this PR)
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.
Hi @silviodonato , thanks for the tips. Regarding the clone comment if you wish I can change it and commit. Let me know if I should do it or not.
For the untracked vs tracked parameters I have simply followed what was already there for the others, I have no strong feeling about it.
+1 |
@silviodonato I can create a general PR modifying all the python config files in DQM packages if needed, including those at Online. About tracked/untracked parameters, the Provenance is lost in DQM plain root files which are the final endproduct of DQM modules after harvesting, right? Though it might be tracked up in the EDM root files for intermediate MEs not produced in Harvesting step |
It is not urgent, but it would be a nice style improvement. Reco is making many PRs in that direction (eg. #30947)
Ok, good point. I thought that it might be important to know if the module ran with useLockRecords True or False but, as you said, we cannot have this piece of information in plain DQM ROOT files. |
OK, I will take care of this cloning restyling for master branch in the near future. Thanks! |
About the tracked or untracked parameter, I do not think It would be interest anyway in keep track of it. It is something which does not affect the beamspot computation per se. |
PR description:
I have added the possibility to lock a record
PR validation:
tested with unitTest
if this PR is a backport please specify the original PR and why you need to backport that PR: