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

first DQM based HLT MET monitoring code #17231

Merged
merged 8 commits into from Feb 8, 2017

Conversation

mtosi
Copy link
Contributor

@mtosi mtosi commented Jan 20, 2017

it would be great if this code could be integrated in 900pre3
so we can start looking at the code on data during the release validation
this is one of the first PRs towards the setup of the HLT prompt monitoring

@fwyzard @gennai @Martin-Grunewald @ndaci @dmitrijus @vanbesien @silviodonato

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mtosi (mia tosi) for CMSSW_9_0_X.

It involves the following packages:

DQMOffline/Trigger

@cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks.
@battibass, @jhgoh, @calderona, @HuguesBrun, @trocino, @rociovilar this is something you requested to watch as well.
@davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here #13028

#include "CommonTools/TriggerUtils/interface/GenericTriggerEventFlag.h"


double PI = 3.2;
Copy link
Contributor

Choose a reason for hiding this comment

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

3.14159265... is no longer in fashion ?

@mtosi
Copy link
Contributor Author

mtosi commented Jan 20, 2017

for the TH1, I think it is better having it at 3.2 (binning)

@cmsbuild
Copy link
Contributor

Pull request #17231 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again.

double PI = 3.2;
int NPI = 64;
MEbinning phi_binning_{
64, -3.2, 3.2
Copy link
Contributor

Choose a reason for hiding this comment

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

Neither PI nor NPI are actually used, but probably planned to make the above line of magic numbers look better :)

Copy link
Contributor

Choose a reason for hiding this comment

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

@mtosi -please remove these unused variables. Thanks

Copy link
Contributor

Choose a reason for hiding this comment

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

the downside to using 3.2 is that your phi distribution won't be flat...

@cmsbuild
Copy link
Contributor

Pull request #17231 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again.

@dmitrijus
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 24, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/17410/console Started: 2017/01/24 17:23

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

@cmsbuild
Copy link
Contributor

-1

Tested at: b2a3983

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-17231/17410/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 worklfows:
140.53 step2

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

@cmsbuild
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

Pull request #17231 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again.

@mtosi
Copy link
Contributor Author

mtosi commented Feb 8, 2017

@davidlange6 @fwyzard
thanks for your suggestions and comments,
do you think it is better, now ?

@davidlange6
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/17685/console Started: 2017/02/08 11:06

@davidlange6
Copy link
Contributor

yes - though I realize a less confusing name for PI=3.2 is PHI_MAX=3.2 and N_PHI=64

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

Pull request #17231 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again.

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 8, 2017

davidlange6 added a commit that referenced this pull request Feb 8, 2017
first DQM based HLT MET monitoring code
@davidlange6 davidlange6 merged commit fd0f60d into cms-sw:CMSSW_9_0_X Feb 8, 2017
@@ -0,0 +1,32 @@
import FWCore.ParameterSet.Config as cms

from DQMOffline.Trigger.metMonitoring_cfi import metMonitoring
Copy link
Contributor

Choose a reason for hiding this comment

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

Dear developers,

May I ask where this module is located? I couldn't find it in the expected location:

  • DQMOffline/Trigger/python/metMonitoring_cfi.py

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Nice. Thanks @Martin-Grunewald for your reply.

@mtosi
Copy link
Contributor Author

mtosi commented Feb 15, 2017 via email

@fwyzard
Copy link
Contributor

fwyzard commented Feb 15, 2017 via email

@davidlange6
Copy link
Contributor

Hi @mtosi , all
looks like this PR has brought a bunch of printouts - how do we remove them?

nericTriggerEventFlag: METMonitor:PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:32 CET Run: 1 Stream: 1
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MET200_METmonitoring@streamBeginRun 15-Mar-2017 13:09:32 CET Run: 1 Stream: 1
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:32 CET Run: 1 Stream: 1
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu90_PFMHTNoMu90_METmonitoring@streamBeginRun 15-Mar-2017 13:09:32 CET Run: 1 Stream: 1
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:PFMETNoMu90_PFMHTNoMu90_METmonitoring@streamBeginRun 15-Mar-2017 13:09:33 CET Run: 1 Stream: 0
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:33 CET Run: 1 Stream: 0
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MET200_METmonitoring@streamBeginRun 15-Mar-2017 13:09:33 CET Run: 1 Stream: 0
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:33 CET Run: 1 Stream: 0
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu90_PFMHTNoMu90_METmonitoring@streamBeginRun 15-Mar-2017 13:09:33 CET Run: 1 Stream: 0
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:PFMETNoMu90_PFMHTNoMu90_METmonitoring@streamBeginRun 15-Mar-2017 13:09:34 CET Run: 1 Stream: 2
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:34 CET Run: 1 Stream: 2
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MET200_METmonitoring@streamBeginRun 15-Mar-2017 13:09:34 CET Run: 1 Stream: 2
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu120_PFMHTNoMu120_METmonitoring@streamBeginRun 15-Mar-2017 13:09:34 CET Run: 1 Stream: 2
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG
%MSG-w GenericTriggerEventFlag: METMonitor:MonoCentralPFJet80_PFMETNoMu90_PFMHTNoMu90_METmonitoring@streamBeginRun 15-Mar-2017 13:09:34 CET Run: 1 Stream: 2
Label ExoDQMTrigger not found in DB for 'AlCaRecoTriggerBitsRcd'
%MSG

@davidlange6
Copy link
Contributor

was workflow 1325 step3 for example

@mtosi
Copy link
Contributor Author

mtosi commented Mar 15, 2017 via email

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

7 participants