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

btag@HLT paths modification to be consistent with the new HLT menu #20359

Merged
merged 2 commits into from Sep 12, 2017

Conversation

natalia-korneeva
Copy link
Contributor

Minor modification of names of HLT paths to monitor.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2017

A new Pull Request was created by @natalia-korneeva (Natalia Korneeva) for master.

It involves the following packages:

HLTriggerOffline/Btag

@kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please review it and eventually sign? Thanks.
@imarches, @mtosi, @acaudron, @JyothsnaKomaragiri, @mverzett, @ferencek, @pvmulder this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20359/473

'HLT_PFHT380_SixJet32_DoubleBTagCSV_',
'HLT_PFMET120_PFMHT120_IDTight_v',
'HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v',
'HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_',
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v
?

@@ -4,7 +4,7 @@
#denominator trigger
hltBtagTriggerSelection = cms.EDFilter( "TriggerResultsFilter",
triggerConditions = cms.vstring(
"HLT_PFMET120_* OR HLT_HT300PT30_QuadJet_75_60_45_40_v* OR HLT_PFHT380_SixJet32_DoubleBTagCSV_* OR HLT_Ele28_eta2p1_WPTight_Gsf_HT150_* OR HLT_IsoMu24_eta2p1_*"),
"HLT_PFMET120_PFMHT120_IDTight_v* OR HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v* OR HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_* OR HLT_Ele28_eta2p1_WPTight_Gsf_HT150_* OR HLT_IsoMu24_eta2p1_v*"),
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't it be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v

'HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v',
'HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v',
'HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v',
'HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_',
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't it be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v

Copy link
Contributor

Choose a reason for hiding this comment

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

was this question resolved? @natalia-korneeva

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@davidlange6 yes as @mtosi agrees with my point and doesn't insist on finishing with _v

'HLT_PFHT380_SixJet32_DoubleBTagCSV_',
'HLT_PFMET120_PFMHT120_IDTight_v',
'HLT_PFHT300PT30_QuadPFJet_75_60_45_40_v',
'HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_',
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't it be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v

hltCombinedSecondaryVertexBJetTagsCalo

HLT_PFHT380_SixJet32_DoubleBTagCSV_:
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_:
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't it be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v

hltFastPrimaryVertex
hltFastPVPixelVertices
hltVerticesL3

HLT_PFHT380_SixJet32_DoubleBTagCSV_:
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_:
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't it be
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_v

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mtosi in this case it should be HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_2p2_v , but in the previous version it was HLT_PFHT380_SixJet32_DoubleBTagCSV_p075_v, so keeping in mind possible future changes I would leave this path as is (without 2p2_v)

hltCombinedSecondaryVertexBJetTagsCalo

HLT_PFHT380_SixJet32_DoubleBTagCSV_:
HLT_PFHT380_SixPFJet32_DoublePFBTagCSV_:
hltCombinedSecondaryVertexBJetTagsCalo

HLT_Ele28_eta2p1_WPTight_Gsf_HT150_:
Copy link
Contributor

Choose a reason for hiding this comment

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

are you sure about this ?
shouldn't it be
HLT_Ele28_eta2p1_WPTight_Gsf_HT150_v

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, there is only one HLT path that could be found with this pattern. To be more strict it is of course possible to add _v

@mtosi
Copy link
Contributor

mtosi commented Sep 4, 2017

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 4, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/22686/console Started: 2017/09/04 11:25

@mtosi
Copy link
Contributor

mtosi commented Sep 4, 2017 via email

@natalia-korneeva
Copy link
Contributor Author

@mtosi yes, everything is fine, I've got all the histograms successfully filled.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 4, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 4, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

Pull request #20359 was updated. @kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please check and sign again.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20359/507

@mtosi
Copy link
Contributor

mtosi commented Sep 5, 2017 via email

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

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

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 5, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2652479
  • DQMHistoTests: Total failures: 195
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2652095
  • DQMHistoTests: Total skipped: 189
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 14 edm output root files, 26 DQM output files

@dmitrijus
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

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, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2)

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit f5b098a into cms-sw:master Sep 12, 2017
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

6 participants