Skip to content
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

Merged
merged 2 commits into from May 13, 2021

Conversation

gennai
Copy link
Contributor

@gennai gennai commented May 7, 2021

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:

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2021

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33659/22551

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2021

A new Pull Request was created by @gennai (simone gennai) for master.

It involves the following packages:

DQM/BeamMonitor
DQM/Integration

@andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please review it and eventually sign? Thanks.
@threus, @batinkov, @battibass this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@jfernan2
Copy link
Contributor

jfernan2 commented May 7, 2021

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2021

-1

Failed Tests: Build Python3
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f6f4b1/14944/summary.html
COMMIT: 7e321e5
CMSSW: CMSSW_12_0_X_2021-05-06-2300/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/33659/14944/install.sh to create a dev area with all the needed externals and cmssw changes.

Build

I 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'...

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2021

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33659/22557

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2021

Pull request #33659 was updated. @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please check and sign again.

@gennai
Copy link
Contributor Author

gennai commented May 10, 2021

@jfernan2 could you trigger the test, or is there anything else I should do for the warnings?

@jfernan2
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f6f4b1/14974/summary.html
COMMIT: 1982ccf
CMSSW: CMSSW_12_0_X_2021-05-10-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/33659/14974/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 37
  • DQMHistoTests: Total histograms compared: 2663174
  • DQMHistoTests: Total failures: 12
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 2663139
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.004 KiB( 36 files compared)
  • DQMHistoSizes: changed ( 312.0 ): -0.004 KiB MessageLogger/Warnings
  • Checked 155 log files, 37 edm output root files, 37 DQM output files
  • TriggerResults: no differences found

@jfernan2
Copy link
Contributor

@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

@gennai
Copy link
Contributor Author

gennai commented May 10, 2021

I am already working on it, I was waiting this PR to be scrutinized to apply the same comments to the back porting

@gennai
Copy link
Contributor Author

gennai commented May 10, 2021

Backporting is #33684

Best,
S.

@jfernan2
Copy link
Contributor

Thank you! @gennai

@jfernan2
Copy link
Contributor

+1
Backport tested succesfully in Online DQM at P5

@cmsbuild
Copy link
Contributor

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)

Copy link
Contributor

@silviodonato silviodonato left a 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");
Copy link
Contributor

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)

Copy link
Contributor Author

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.

@silviodonato
Copy link
Contributor

+1
I got confused with FakeBeamMonitor.cc that was made recently.
So I forward the comments to @cms-sw/dqm-l2.
Ideally the untracked parameters should be used only for those parameters that does not change the physics result.

@cmsbuild cmsbuild merged commit d7fa76b into cms-sw:master May 13, 2021
@jfernan2
Copy link
Contributor

jfernan2 commented May 13, 2021

@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

@silviodonato
Copy link
Contributor

@silviodonato I can create a general PR modifying all the python config files in DQM packages if needed, including those at Online.

It is not urgent, but it would be a nice style improvement. Reco is making many PRs in that direction (eg. #30947)

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

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.

@jfernan2
Copy link
Contributor

OK, I will take care of this cloning restyling for master branch in the near future. Thanks!

@gennai
Copy link
Contributor Author

gennai commented May 16, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants