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

Add plots for displaced muon quantities to uGMT DQM #31951

Merged
merged 7 commits into from Nov 4, 2020

Conversation

dinyar
Copy link
Contributor

@dinyar dinyar commented Oct 27, 2020

PR description:

In Run-3 displaced muon data are received from BMTF and forwarded to the uGT. This PR adds plots for these quantities to the uGMT DQM.

PR validation:

Ran the DQM on lxplus and verified that the new plots showed up. Checked that the old plots are still there and populated.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31951/19408

  • This PR adds an extra 32KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @dinyar (Dinyar Rabady) for master.

It involves the following packages:

DQM/L1TMonitor

@andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@dinyar
Copy link
Contributor Author

dinyar commented Oct 27, 2020

attn @rekovic

@jfernan2
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 27, 2020

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+1
Tested at: 9994878
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7a6eb7/10331/summary.html
CMSSW: CMSSW_11_2_X_2020-10-27-1100
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7a6eb7/10331/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2544092
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 395
  • DQMHistoTests: Total successes: 2543668
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 913.936 KiB( 34 files compared)
  • DQMHistoSizes: changed ( 10024.0,... ): 37.059 KiB L1TEMU/L1TdeStage2uGMT
  • DQMHistoSizes: changed ( 10024.0,... ): 15.750 KiB L1T/L1TStage2uGMT
  • DQMHistoSizes: changed ( 10024.0,... ): 4.312 KiB L1T/L1TStage2uGT
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@jfernan2
Copy link
Contributor

@dinyar just for my understanding, the new plots should monitor Run3 smaples, but they seem to be added on almost any sample, even Run1 ones
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_11_2_X_2020-10-27-1100+7a6eb7/39605/dqm-histo-comparison-summary.html
Is this expected?

@dinyar
Copy link
Contributor Author

dinyar commented Oct 28, 2020

Hi @jfernan2,

Yes, that's true. Is there a way to avoid them being generated for older samples? We need them for the run-3 online DQM and I'd say also relvals, but otherwise not.

Cheers,
Dinyar

@jfernan2
Copy link
Contributor

You would need to create a new L1T DQM module with just the Run3 plots and then enable in DQMOffline config file like (e.g.) GEM is doing:

from Configuration.Eras.Modifier_run3_GEM_cff import run3_GEM

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 1, 2020

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

@jfernan2
Copy link
Contributor

jfernan2 commented Nov 3, 2020

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2020

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2020

+1
Tested at: b53fa4a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7a6eb7/10469/summary.html
CMSSW: CMSSW_11_2_X_2020-11-02-2300
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 3, 2020

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7a6eb7/10469/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2544092
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 24
  • DQMHistoTests: Total successes: 2544039
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 42.046 KiB( 34 files compared)
  • DQMHistoSizes: changed ( 11634.0,... ): 12.207 KiB L1TEMU/L1TdeStage2uGMT
  • DQMHistoSizes: changed ( 11634.0,... ): 8.816 KiB L1T/L1TStage2uGMT
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@jfernan2
Copy link
Contributor

jfernan2 commented Nov 3, 2020

@dinyar can you please make a last check that all the changes inrtroduced are what you expect?
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_11_2_X_2020-11-02-2300+7a6eb7/39697/dqm-histo-comparison-summary.html
Thanks

@dinyar
Copy link
Contributor Author

dinyar commented Nov 4, 2020

Hi @jfernan2,

I had a look and things look as expected now. (Some mismatches are seen in the Run-3 plots, but these can be explained by the fact that the BMTF packer hasn't been updated to work for the Run-3 data format yet.)

One thing I noticed is that the first time I entered some of the folders I got and icon with three exclamation marks instead of a plot. When I went into the folder above and re-entered the expected plot was there. I assume this was some glitch in the machinery and not in my code, but wanted to mention it for completeness.

Cheers,
Dinyar

@jfernan2
Copy link
Contributor

jfernan2 commented Nov 4, 2020

One thing I noticed is that the first time I entered some of the folders I got and icon with three exclamation marks instead of a plot. When I went into the folder above and re-entered the expected plot was there. I assume this was some glitch in the machinery and not in my code, but wanted to mention it for completeness.

Yes, this is a temporary glitch from DQM GUI, new GUI in development is indeed fixing that behaviour.

I proceed to approve the PR given your green light. Please do not forget to create a backport in 11_1_X to have these changes in the next MWGR

@jfernan2
Copy link
Contributor

jfernan2 commented Nov 4, 2020

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 4, 2020

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)

@silviodonato
Copy link
Contributor

+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.

None yet

4 participants