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
[DQMOffline/Trigger] improved DQM plugin for monitoring of HLT path/filter efficiencies #29095
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29095/13994
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages: DQMOffline/Trigger @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 42a848b CMSSW: CMSSW_11_1_X_2020-03-04-1100 I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following workflows: runTheMatrix-results/140.53_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI/step2_RunHI2011+RunHI2011+RECOHID11+HARVESTDHI.log |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
I think the 2 lines removed in the last commit were previously having no effect ( |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29095/14005
|
Pull request #29095 was updated. @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
thank you @missirol! |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
fwiw, I didn't catch something obviously incorrect in the new outputs; the efficiency values themselves are harder to judge because of the limited stats, but things look as expected. |
+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. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is meant as an improvement of the DQM plugin used to monitor the efficiencies of all HLT paths in a given HLT-Menu, as well as the efficiencies of the individual filters making up a given (HLT) path.
Currently, this monitoring is done by the plugin
GeneralHLTOffline
, which builds a set of histograms (TH1F
s) counting how many times a given trigger fired, and how many times a given filter was executed.The PR replaces
GeneralHLTOffline
with a new plugin namedHLTFiltersDQMonitor
, which serves the same purpose, but produces DQM outputs in a slightly different format.In
HLTFiltersDQMonitor
,TProfile
s are used to obtain efficiencies, of either a trigger path or an individual filter; this (i.e. using efficiencies viaTProfile
s instead of counts viaTH1F
s) allows to make comparisons straightforward between runs/samples with different number of events; usingTProfile
s also allows to have the efficiency estimates directly, i.e. without any dedicated harvesting of these DQM outputs (thanks to @schneiml for the suggestion to useTProfile
s). More specifically, the new DQM outputs (underHLT/Filters/
) includeSince the PR changes the format of these DQM outputs (from counts to efficiencies), the comparisons will not be very meaningful; we will instead have to check the new outputs and verify that they are in agreement with expectations (an apples-to-apples comparison to the outputs of
GeneralHLTOffline
would not be possible anyway, because of a couple of fixesincluded in the new plugin, with respect to the old one).
The new plugin was validated with a number of local tests with MC, but it will be useful to check what happens when testing it on a larger scale during the PR review.
The changes in
test/
are mostly just renaming, for consistency, to accommodate for the new plugin (most of the configs intest/
seem fairly old anyway).FYI @Sam-Harper @gennai
PR validation:
Successfully ran a few standard workflows, e.g.
runTheMatrix.py -l 11634.0
.