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

[12_5_X] Use Era Run3_pp_on_PbPb_approxSiStripClusters in DQM clients with tracking #39975

Merged

Conversation

francescobrivio
Copy link
Contributor

@francescobrivio francescobrivio commented Nov 3, 2022

PR description:

Backport of #39988

Following the addition of a new Era (Run3_pp_on_PbPb_approxSiStripClusters) in #39863, this PR updates the Era in the online DQM clients that use tracking in order to properly cope with the approxSiStripClusters.
@mmusich please advise if I forgot any, or if other modifications are needed

@cms-sw/dqm-l2 I believe this is the only way to properly handle the HI run, but if you have a better plan please let me know and I can update the PR

- Note1 -
Unfortunately I don't know if a cms.Process() can be customized with a different Era (e.g. following a check on the runKey) after it has been initialized with another one (I guess not, but maybe @makortel @Dr15Jones can advise), so the hardcoded solution in this PR is to completely change the Era to the approxSiStripClusters one.
Hence this PR should not be merged, but only applied online in DQM machines in P5 for the HI data taking period (currently scheduled for 17-18th November).

EDIT: I'm now using the sys.argv to determine the run key and set the proper Era when the cms.Process() is declared,
so this PR should be good for both HI and pp collisions and thus can be merged.

- Note2 -
Visualization clients make use of scenarios, they will be modified in a different PR which includes a new scenario (working on it right now).

PR validation:

Tested locally with:
cmsRun DQM/Integration/python/clients/beam_dqm_sourceclient-live_cfg.py unitTest=True runkey=hi_run
with the HI input streamer files provided in this CMSTalk thread.

Backport:

Backport of #39988

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2022

A new Pull Request was created by @francescobrivio for CMSSW_12_5_X.

It involves the following packages:

  • DQM/Integration (dqm)

@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @syuvivida, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks.
@threus, @batinkov, @battibass this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@francescobrivio
Copy link
Contributor Author

FYI @cms-sw/alca-l2 @cms-sw/tracking-pog-l2 @mandrenguyen

@rvenditti
Copy link
Contributor

please test

@Dr15Jones
Copy link
Contributor

Unfortunately I don't know if a cms.Process() can be customized with a different Era (e.g. following a check on the runKey) after it has been initialized with another one

It can not be. The Modifiers (which is what Era's use) are applied as we load python modules so one can not change what Modifiers are to be used once the Process has started to be built.

@francescobrivio
Copy link
Contributor Author

Unfortunately I don't know if a cms.Process() can be customized with a different Era (e.g. following a check on the runKey) after it has been initialized with another one

It can not be. The Modifiers (which is what Era's use) are applied as we load python modules so one can not change what Modifiers are to be used once the Process has started to be built.

Ok got it! thanks Chris!
@cms-sw/dqm-l2 then I believe this PR is the only way we have to apply the proper era for HI online.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2022

-1

Failed Tests: UnitTests RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f0daa8/28773/summary.html
COMMIT: ca3bd49
CMSSW: CMSSW_12_5_X_2022-11-03-1100/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/39975/28773/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found errors in the following unit tests:

---> test TestDQMOnlineClient-beam_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-sistrip_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-pixel_dqm_sourceclient had ERRORS

RelVals-INPUT

The relvals timed out after 4 hours.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 17 differences found in the comparisons
  • DQMHistoTests: Total files compared: 51
  • DQMHistoTests: Total histograms compared: 3734344
  • DQMHistoTests: Total failures: 1010
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3733312
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 50 files compared)
  • Checked 216 log files, 49 edm output root files, 51 DQM output files
  • TriggerResults: no differences found

@francescobrivio
Copy link
Contributor Author

-1

Failed Tests: UnitTests RelVals-INPUT Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f0daa8/28773/summary.html COMMIT: ca3bd49 CMSSW: CMSSW_12_5_X_2022-11-03-1100/el8_amd64_gcc10 User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/39975/28773/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found errors in the following unit tests:

---> test TestDQMOnlineClient-beam_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-sistrip_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-pixel_dqm_sourceclient had ERRORS

RelVals-INPUT

The relvals timed out after 4 hours.

Comparison Summary

Summary:

* No significant changes to the logs found

* Reco comparison results: 17 differences found in the comparisons

* DQMHistoTests: Total files compared: 51

* DQMHistoTests: Total histograms compared: 3734344

* DQMHistoTests: Total failures: 1010

* DQMHistoTests: Total nulls: 0

* DQMHistoTests: Total successes: 3733312

* DQMHistoTests: Total skipped: 22

* DQMHistoTests: Total Missing objects: 0

* DQMHistoSizes: Histogram memory added: 0.0 KiB( 50 files compared)

* Checked 216 log files, 49 edm output root files, 51 DQM output files

* [TriggerResults](https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_5_X_2022-11-03-1100+f0daa8/53887/triggerResults): no differences found

Ok as expected this does not run on old data, but @makortel suggested privately a way around this.
I will test it and push it as soon as I manage.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 4, 2022

Pull request #39975 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @syuvivida, @pmandrik, @micsucmed, @rvenditti can you please check and sign again.

@francescobrivio
Copy link
Contributor Author

In the last push I'm using the sys.argvto get the running conditions (hi_run for the HI collisions) and set the correct Era
to be used for HI or for pp.

With this last commit tests should pass and this PR can even be integrated in the release, provided @cms-sw/dqm-l2 agrees. I will also open the master PR.

@francescobrivio
Copy link
Contributor Author

@cmsbuild please test

@francescobrivio francescobrivio changed the title [Do not merge] Use Era Run3_pp_on_PbPb_approxSiStripClusters in DQM online clients Use Era Run3_pp_on_PbPb_approxSiStripClusters in DQM clients with tracking Nov 4, 2022
@mmusich
Copy link
Contributor

mmusich commented Nov 4, 2022

Hence this PR should not be merged, but only applied online in DQM machines in P5 for the HI data taking period (currently scheduled for 17-18th November).

I guess this doesn't apply anymore.

@francescobrivio
Copy link
Contributor Author

Hence this PR should not be merged, but only applied online in DQM machines in P5 for the HI data taking period (currently scheduled for 17-18th November).

I guess this doesn't apply anymore.

I just updated the description :D

@francescobrivio francescobrivio changed the title Use Era Run3_pp_on_PbPb_approxSiStripClusters in DQM clients with tracking [12_5_X] Use Era Run3_pp_on_PbPb_approxSiStripClusters in DQM clients with tracking Nov 4, 2022
@francescobrivio
Copy link
Contributor Author

backport of #39988

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 4, 2022

Pull request #39975 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @syuvivida, @pmandrik, @micsucmed, @rvenditti can you please check and sign again.

@francescobrivio
Copy link
Contributor Author

@cmsbuild please test

@francescobrivio
Copy link
Contributor Author

urgent

  • needed in the next 12_5_X release for HI data-taking

@cmsbuild cmsbuild added the urgent label Nov 7, 2022
@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 7, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f0daa8/28819/summary.html
COMMIT: 33c8378
CMSSW: CMSSW_12_5_X_2022-11-06-2300/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/39975/28819/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: 2 differences found in the comparisons
  • DQMHistoTests: Total files compared: 51
  • DQMHistoTests: Total histograms compared: 3734658
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3734628
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.004 KiB( 50 files compared)
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 216 log files, 49 edm output root files, 51 DQM output files
  • TriggerResults: no differences found

@emanueleusai
Copy link
Member

PR added on top of 12_5_2 to online machines and tested successfully during the HI run

@emanueleusai
Copy link
Member

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 7, 2022

This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

perrotta commented Nov 9, 2022

+1

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.

7 participants