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 new CaloL1 offline DQM module and configuration #31678

Closed
wants to merge 4 commits into from

Conversation

aloeliger
Copy link
Contributor

PR description:

A new CaloL1 DQM offline module in "Global" format has been introduced to comply with the concurrent LS processing introduced for the offline DQM as a part of #25090. This offline module is largely a duplicate of the online version of the L1TStage2CaloLayer1 module, but with 7 monitoring elements removed, and changed to be a DQMGlobalEDAnalyzer instead of DQMOneEDAnalyzer. Monitoring elements have been moved to a dedicated CaloL1Information namespace and data structure as part of the DQMGlobalEDAnalyzer template. A duplicate of the online _cfi.py has been created for the offline module, and the overall offline L1DQM sequence L1TriggerDqmOffline_cff.py has been adjusted to add this module into the offline workflow.

PR validation:

All code compiles, and I have checked that a min bias data workflow reproduces the same histograms between the old online module and new offline module. I have also checked runTheMatrix test workflows and any failures seem due to failing to find or open remote files. As well, the PR seems to pass the basic test procedure suggested in the CMSSW PR instructions.

if this PR is a backport please specify the original PR and why you need to backport that PR:

This PR is not a backport

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31678/18812

  • This PR adds an extra 24KB to repository

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31678/18816

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

A new Pull Request was created by @aloeliger for master.

It involves the following packages:

DQMOffline/L1Trigger

@benkrikler, @kmaeshima, @andrius-k, @ErnestaP, @cmsbuild, @rekovic, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks.
@rociovilar 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

@silviodonato
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

The tests are being triggered in jenkins.

#ifndef L1TStage2CaloLayer1Offline_H
#define L1TStage2CaloLayer1Offline_H

//change from "One" to "Global"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can remove this kind of comments. Perhaps you can write a general comment saying that this is almost a duplicate of the online version of the L1TStage2CaloLayer1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can go change this. Will this require the code checks and tests be restarted?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, when you push the changes to your repository, the code-checks will start again automatically.
Please remove all comments similar to this one
Example:
//#include "DQMServices/Core/interface/DQMOneEDAnalyzer.h"
or
//Elements removed from online version of module. [...]

@silviodonato
Copy link
Contributor

@aloeliger Could you explain why you are adding a new modules instead of modifying L1TStage2CaloLayer1?

@aloeliger
Copy link
Contributor Author

@silviodonato There are seven luminosity block transition based monitoring elements that are not compatible with the change from DQMOneEDAnalyzer<edm::one::WatchLuminosityBlocks> to DQMGlobalEDAnalzyer<> these are:

  1. last20Mismatches_: A monitoring element that was read back at the beginning of luminosity blocks detailing the last 20 mismatches by type (ECAL/HCAL and fine grain and feature versus other) and run, luminosity section and event.
  2. maxEvtLinkErrorsByLumi(E/H)CAL_ and maxEvtLinkErrorsByLumi_: these 3 are monitoring elements that track the max number of link errors seen in an event for ECAL, HCAL or both for a given luminosity section. These were filled at the end of a luminosity block, and the information needed to do this would need to be shared across streams
  3. maxEvtMismatchByLumi(E/H)CAL_ and maxEvtMismatchByLumi:_ These 3 are monitoring elements similar to the above, but for trigger mismatches.

The CaloL1 team was reluctant to change monitoring elements used for online monitoring, so for a compromise I left online monitoring unchanged and introduced a slightly changed duplicate for a multithreaded use for offline DQM.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

-1

Tested at: 9330df8

CMSSW: CMSSW_11_2_X_2020-10-05-2300
SCRAM_ARCH: slc7_amd64_gcc820
You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d0c5b3/9753/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests

  • Unit Tests:

I found errors in the following unit tests:

---> test TestDQMOfflineConfiguration0 had ERRORS

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 19, 2020

The tests are being triggered in jenkins.
Tested with other pull request(s) #31699,#31689

@cmsbuild
Copy link
Contributor

-1

Tested at: befefd9

CMSSW: CMSSW_11_2_X_2020-10-19-1100
SCRAM_ARCH: slc7_amd64_gcc820
You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-60df14/10081/summary.html

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following workflows:
4.22 step5

runTheMatrix-results/4.22_RunCosmics2011A+RunCosmics2011A+RECOCOSD+ALCACOSD+SKIMCOSD+HARVESTDC/step5_RunCosmics2011A+RunCosmics2011A+RECOCOSD+ALCACOSD+SKIMCOSD+HARVESTDC.log

140.53 step3
runTheMatrix-results/140.53_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI/step3_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI.log

8.0 step5
runTheMatrix-results/8.0_BeamHalo+BeamHalo+DIGICOS+RECOCOS+ALCABH+HARVESTCOS/step5_BeamHalo+BeamHalo+DIGICOS+RECOCOS+ALCABH+HARVESTCOS.log

4.53 step4
runTheMatrix-results/4.53_RunPhoton2012B+RunPhoton2012B+HLTD+RECODR1reHLT+HARVESTDR1reHLT/step4_RunPhoton2012B+RunPhoton2012B+HLTD+RECODR1reHLT+HARVESTDR1reHLT.log

9.0 step4
runTheMatrix-results/9.0_Higgs200ChargedTaus+Higgs200ChargedTaus+DIGI+RECO+HARVEST/step4_Higgs200ChargedTaus+Higgs200ChargedTaus+DIGI+RECO+HARVEST.log

25.0 step4
runTheMatrix-results/25.0_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT/step4_TTbar+TTbar+DIGI+RECOAlCaCalo+HARVEST+ALCATT.log

136.731 step4
runTheMatrix-results/136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2/step4_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2.log

25202.0 step4
runTheMatrix-results/25202.0_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25+NANOUP15_PU25/step4_TTbar_13+TTbar_13+DIGIUP15_PU25+RECOUP15_PU25+HARVESTUP15_PU25+NANOUP15_PU25.log

@cmsbuild
Copy link
Contributor

Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped)

@silviodonato
Copy link
Contributor

The previous test was done just to check that the framework does not complain anymore about The following modules require synchronizing on LuminosityBlock boundaries of L1TStage2CaloLayer1. The test was successful.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 19, 2020

The tests are being triggered in jenkins.
Tested with other pull request(s) #31699,#31689,#31829

@cmsbuild
Copy link
Contributor

+1
Tested at: befefd9
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2a187a/10096/summary.html
CMSSW: CMSSW_11_2_X_2020-10-19-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-2a187a/10096/summary.html

Comparison Summary:

  • You potentially added 4870 lines to the logs
  • Reco comparison results: 7 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2543640
  • DQMHistoTests: Total failures: 28
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2543590
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -773.364 KiB( 34 files compared)
  • DQMHistoSizes: changed ( 10024.0,... ): -48.369 KiB L1T/L1TStage2CaloLayer1
  • DQMHistoSizes: changed ( 136.731 ): -47.829 KiB L1T/L1TStage2CaloLayer1
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@silviodonato
Copy link
Contributor

@aloeliger @cms-sw/dqm-l2 @cms-sw/l1-l2 what is the status of this PR? Is it ready to be merged?

@aloeliger
Copy link
Contributor Author

aloeliger commented Nov 2, 2020

@aloeliger I notice now that the reportSummary Map becomes orange for CaloLayer 1 and HCAL/ECAL TPG [1] due to this PR since I guess it was based on the MEs you are removing.
I would be good to modify the report so that it does not check for those plots
See what I mean here:
[1] https://tinyurl.com/y52ltpuo

@aloeliger @cms-sw/dqm-l2 @cms-sw/l1-l2 what is the status of this PR? Is it ready to be merged?

@silviodonato, @jfernan2, apologies again for my schedule, but now that Higgs2020 is done, I have talked to the CaloL1 team about a new fix that maintains the summary reports that were broken in this PR/solution. I have opened a new PR #32004 with changes exclusively to the online CaloL1 DQM that does not require this separate offline module or any changes to any configurations. At this point, I think this PR is no longer necessary, and could be safely closed in favor of #32004.

@silviodonato
Copy link
Contributor

moved to #32004

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.

4 participants