-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Adding HLT_Ele50_CaloIdVT_GsfTrkIdT_PFJet165_v* to B2G HLT Monitoring #19407
Conversation
A new Pull Request was created by @UBParker (Ashley Marie Parker) for master. It involves the following packages: DQMOffline/Trigger @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
tracked by #19142 |
please, rebase |
, muoToken_ ( mayConsume<reco::MuonCollection> (iConfig.getParameter<edm::InputTag>("muons") ) ) | ||
, vtxToken_ ( mayConsume<reco::VertexCollection> (iConfig.getParameter<edm::InputTag>("vertices") ) ) | ||
, ht_variable_binning_ ( iConfig.getParameter<edm::ParameterSet>("histoPSet").getParameter<std::vector<double> >("htBinning") ) | ||
, ht_binning_ ( getHistoPSet (iConfig.getParameter<edm::ParameterSet>("histoPSet").getParameter<edm::ParameterSet> ("htPSet") ) ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you really need it ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, this was already present, I did not change it. If it is not needed I can remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtosi - I don't understand what are you pointing to exactly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need to squeeze the #bins,
=> if the fix size binning is not needed, because you have the variable binning already
please, drop the fix one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sudhaahuja Can you tell me which lines to remove ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay in checking the compilation errors, but I was traveling for EPS and now attending the conference.
@mtosi - we (me and @UBParker ) removed the fixed binning but then we realised that htvsLS 2D histogram depends on fixed binning, so we changed the definition of this histogram as - variable binning vs LS 2D histogram (https://github.com/UBParker/cmssw/blob/AddingHLTEl50PFJet165/DQMOffline/Trigger/plugins/METMonitor.cc#L117-#L126). I think the compilation error is coming because its not defined in the header (.h) file. After adding that in the .h file, I am trying to compile it locally but now I see that kind of format is not defined in the DQMServices/Core/interface/DQMStore.h file. So can we just keep the fixed binning definition for the htvsLS plot and also similarly for the metvsLS plot.
for ( auto const & j : *jetHandle ) { | ||
if ( jetSelection_( j ) ) { | ||
jets.push_back(j); | ||
if ( jetSelection_HT_(j)) ht += j.pt(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please, move outside the jetSelection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or better, drop this line !
it is already in l171 !!!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@UBParker - could you please remove this L167 from the old commit versions, as the jetSelection_HT_ was already moved to L171 in the recent commits by @rappoccio I think. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
iEvent.getByToken(vtxToken_, vtxHandle); | ||
|
||
reco::Vertex vtx; | ||
math::XYZPoint pv(0, 0, 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why don't you make use of the beam spot if the PV is not available/valid ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code was already present before I began working on this. If you would like me to make use of beam spot and if @rappoccio agrees that this is a necessary update then I will implement it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sudhaahuja Can you comment on this?
std::vector<reco::Muon> muons; | ||
muons.clear(); | ||
for ( auto const & m : *muoHandle ) { | ||
if ( muoSelection_( m ) && m.isGlobalMuon() && m.isPFMuon() && m.globalTrack()->normalizedChi2() < 10. && m.globalTrack()->hitPattern().numberOfValidMuonHits() > 0 && m.numberOfMatchedStations() > 1 && fabs(m.muonBestTrack()->dxy(pv)) < 0.2 && fabs(m.muonBestTrack()->dz(pv)) < 0.5 && m.innerTrack()->hitPattern().numberOfValidPixelHits() > 0 && m.innerTrack()->hitPattern().trackerLayersWithMeasurement() > 5 ) muons.push_back(m); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no hardcoded selection, please
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as METMonitor, @mtosi - For calculating the efficiency of certain triggers, there is a requirement to select one tight muon (while using the singleMuon dataset). Also, its was not possible to define the same selection cuts in the cff files so I put them here instead. Also, I can not use the function "isTightMuon()" directly, so I put in the tight muon selection cuts one by one in the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please, add a flag in order to switch ON these selections
iEvent.getByToken(vtxToken_, vtxHandle); | ||
|
||
reco::Vertex vtx; | ||
math::XYZPoint pv(0, 0, 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as in HTMonitor, why don't you use the beam spot ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sudhaahuja Can you comment on this? I have not edited this file.
for ( auto const & m : *muoHandle ) { | ||
if ( muoSelection_( m ) ) muons.push_back(m); | ||
bool pass = m.isGlobalMuon() && m.isPFMuon() && m.globalTrack()->normalizedChi2() < 10. && m.globalTrack()->hitPattern().numberOfValidMuonHits() > 0 && m.numberOfMatchedStations() > 1 && fabs(m.muonBestTrack()->dxy(pv)) < 0.2 && fabs(m.muonBestTrack()->dz(pv)) < 0.5 && m.innerTrack()->hitPattern().numberOfValidPixelHits() > 0 && m.innerTrack()->hitPattern().trackerLayersWithMeasurement() > 5; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no hard coded selection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have asked @sudhaahuja to reply to these comments as only the files with "B2G" in the title are those I actually edited for this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtosi - For calculating the efficiency of certain triggers, there is a requirement to select one tight muon (while using the singleMuon dataset). Also, its was not possible to define the same selection cuts in the cff files so I put them here instead. Also, I can not use the function "isTightMuon()" directly, so I put in the tight muon selection cuts one by one in the code.
), | ||
|
||
efficiencyProfile = cms.untracked.vstring( | ||
"effic_pfjetpT_vs_LS 'JET efficiency vs LS; LS; PF JET efficiency' jetpTVsLS_numerator jetpTVsLS_denominator", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you really need it ?
are you applying different selection w.r.t. the HT one ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it is the same. I have fixed this here https://github.com/UBParker/cmssw/blob/AddingHLTEl50PFJet165/DQMOffline/Trigger/python/B2GMonitoring_Client_cff.py
# HLT_AK8PFHT700_TrimR0p1PT0p03Mass50 | ||
AK8PFHT750_TrimMass50_HTmonitoring = hltHTmonitoring.clone() | ||
AK8PFHT750_TrimMass50_HTmonitoring.FolderName = cms.string('HLT/B2GMonitor/AK8PFHT750_TrimMass50') | ||
AK8PFHT750_TrimMass50_HTmonitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_AK8PFHT750_TrimMass50_v*") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't you monitor the SD mass and tau2/tau1 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not at trigger level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not at trigger level, as none of the quantities in these plots, i would say...
shouldn't you monitor the bias on these very important quantities in your analyses ?!?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are analysis dependent. I would say that the HLT monitoring we want should be more directly related to the trigger than to individual analyses, no?
@@ -9,13 +12,35 @@ | |||
"effic_met 'MET turnON; PF MET [GeV]; efficiency' met_numerator met_denominator", | |||
"effic_met_variable 'MET turnON; PF MET [GeV]; efficiency' met_variable_numerator met_variable_denominator", | |||
"effic_metPhi 'MET efficiency vs phi; PF MET phi [rad]; efficiency' metPhi_numerator metPhi_denominator", | |||
"effic_ht 'HT turnON; PF HT [GeV]; efficiency' ht_numerator ht_denominator", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtosi Could you clarify? Maybe @sudhaahuja could comment on any questions you have about this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this turnOn done in an other client as well ?!?
the B2G monitor client for instance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtosi I have removed this turn on from the B2G client here https://github.com/UBParker/cmssw/blob/AddingHLTEl50PFJet165/DQMOffline/Trigger/python/B2GMonitoring_Client_cff.py
# HLT_PFMETNoMu90_PFMHTNoMu90_IDTight | ||
PFMETNoMu90_PFMHTNoMu90_HTmonitoring = hltHTmonitoring.clone() | ||
PFMETNoMu90_PFMHTNoMu90_HTmonitoring.FolderName = cms.string('HLT/HT/PFMETNoMu90/') | ||
PFMETNoMu90_PFMHTNoMu90_HTmonitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_PFMETNoMu90_PFMHTNoMu90_IDTight_v*") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why I do not see it in the silvio's google doc ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@UBParker - Could you please remove these paths from you cff file. These came from the original template I used and were never deleted. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sudhaahuja I need clarification on which paths to remove, just LT_PFMETNoMu90_PFMHTNoMu90_IDTight or others as well ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@UBParker - can you please remove PFMETNoMu90_PFMHTNoMu90 , MET200 & MonoCentralPFJet80_PFMETNoMu90_PFMHTNoMu90 monitoring from both METMonitor and HTMonitor cff files. Thanks a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mtosi @sudhaahuja I have removed those paths from both files.
please make it configurable
… On 26 Jun 2017, at 18:07, sudha ***@***.***> wrote:
@sudhaahuja commented on this pull request.
In DQMOffline/Trigger/plugins/METMonitor.cc:
> for ( auto const & m : *muoHandle ) {
- if ( muoSelection_( m ) ) muons.push_back(m);
+ bool pass = m.isGlobalMuon() && m.isPFMuon() && m.globalTrack()->normalizedChi2() < 10. && m.globalTrack()->hitPattern().numberOfValidMuonHits() > 0 && m.numberOfMatchedStations() > 1 && fabs(m.muonBestTrack()->dxy(pv)) < 0.2 && fabs(m.muonBestTrack()->dz(pv)) < 0.5 && m.innerTrack()->hitPattern().numberOfValidPixelHits() > 0 && m.innerTrack()->hitPattern().trackerLayersWithMeasurement() > 5;
@mtosi - For calculating the efficiency of certain triggers, there is a requirement to select one tight muon (while using the singleMuon dataset). Also, I can not use the function "isTightMuon()" directly, so I put in the tight muon selection cuts one by one in the code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
are you referring to the SD and tau2/tau1 ?
i tend to agree, but at the same time i think it would be worth
to have at least one representative one
mia
… On 26 Jun 2017, at 19:02, rappoccio ***@***.***> wrote:
@rappoccio commented on this pull request.
In DQMOffline/Trigger/python/B2GMonitoring_cff.py:
> +#from DQMOffline.Trigger.JetMETMonitor_cfi import hltJetMETmonitoring
+from DQMOffline.Trigger.HTMonitor_cfi import hltHTmonitoring
+from DQMOffline.Trigger.B2GTnPMonitor_cfi import B2GegmGsfElectronIDsForDQM,B2GegHLTDQMOfflineTnPSource
+
+# B2G triggers:
+#HLT_AK8PFHT750_TrimMass50_v*
+#HLT_AK8PFJet380_TrimMass30_v*
+#HLT_AK8PFHT800_TrimMass50_v*
+#HLT_AK8PFJet400_TrimMass30_v*
+#HLT_AK8PFHT850_TrimMass50_v*
+#HLT_AK8PFJet420_TrimMass30_v*
+#HLT_AK8PFHT900_TrimMass50_v*
+# HLT_AK8PFHT700_TrimR0p1PT0p03Mass50
+AK8PFHT750_TrimMass50_HTmonitoring = hltHTmonitoring.clone()
+AK8PFHT750_TrimMass50_HTmonitoring.FolderName = cms.string('HLT/B2GMonitor/AK8PFHT750_TrimMass50')
+AK8PFHT750_TrimMass50_HTmonitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_AK8PFHT750_TrimMass50_v*")
These are analysis dependent. I would say that the HLT monitoring we want should be more directly related to the trigger than to individual analyses, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Pull request #19407 was updated. @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @vanbesien, @davidlange6 can you please check and sign again. |
I'm sure at some point @cmsbuild will simply refuse to run the tests |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
-1 Tested at: 491bd35 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: Build ClangBuild
I found an error when building: >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/HTMonitor.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/NoBPTXMonitor.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/HLTTagAndProbeOfflineSource.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/METMonitor.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/RazorMonitor.cc /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/HTMonitor.cc:110:6: error: prototype for 'void HTMonitor::bookME(DQMStore::IBooker&, HTMonitor::HTME&, const string&, const string&, int, double, double, const std::vector&)' does not match any in class 'HTMonitor' void HTMonitor::bookME(DQMStore::IBooker &ibooker, HTME& me, const std::string& histname, const std::string& histtitle,int nbinsX, double xmin, double xmax , const std::vector& binningY) ^ /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/HTMonitor.cc:97:6: error: candidates are: void HTMonitor::bookME(DQMStore::IBooker&, HTMonitor::HTME&, const string&, const string&, const std::vector&, const std::vector&) void HTMonitor::bookME(DQMStore::IBooker &ibooker, HTME& me, const std::string& histname, const std::string& histtitle, const std::vector& binningX, const std::vector& binningY) ^
I found a compilation error while trying to compile with clang: >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/src/JetMETHLTOfflineSource.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/src/HotlineDQM.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/src/TopHLTOfflineDQMHelper.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/src/HLTTauCertifier.cc >> Compiling edm plugin /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/src/EgHLTOffHelper.cc /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/METMonitor.cc:117:18: error: out-of-line definition of 'bookME' does not match any declaration in 'METMonitor' void METMonitor::bookME(DQMStore::IBooker &ibooker, METME& me, const std::string& histname, const std::string& histtitle, int nbinsX, double xmin, double xmax, const std::vector& binningY) ^~~~~~ /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-07-04-1100/src/DQMOffline/Trigger/plugins/METMonitor.cc:152:3: error: no matching member function for call to 'bookME' bookME(ibooker,metVsLS_ ,histname,histtitle,ls_binning_.nbins, ls_binning_.xmin, ls_binning_.xmax, met_variable_binning_ ); ^~~~~~ The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
@sudhaahuja Please test the file DQMOffline/Trigger/plugins/METMonitor.cc and let me know the appropriate changes. These errors are related to the changes you suggested that we make to the file during our meeting on Monday. |
@UBParker Bobae and I are planning to update pure MET Trigger which was suggested by JME Group. We think we just added MET triggers in METMonitor_cff file. (We copied METMonitor_cff.py from this PR and then we added METTriggers. ) If you go to this link[1], you can see our METMonitor_cff.py I'm not sure we can update this file in this PR. Can we update this file? Thank you, |
Can you *please* test the changes locally before pushing them to the PR ?
|
Yes, apologies, those are not my changes though, which is why I have asked @sudhaahuja to test them. |
@physicist87 If you have already tested your changes and others agree @fwyzard @mtosi @rappoccio then I can make the required additions. |
@UBParker Thank you !! |
could not you simply have the parameter, but make use of it only for the 2D
plot ?!?!?!?
…On Thu, Jul 6, 2017 at 10:47 AM, sudha ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In DQMOffline/Trigger/plugins/HTMonitor.cc
<#19407 (comment)>:
> +
+#include "DataFormats/Math/interface/deltaPhi.h"
+
+// -----------------------------
+// constructors and destructor
+// -----------------------------
+
+HTMonitor::HTMonitor( const edm::ParameterSet& iConfig ) :
+ folderName_ ( iConfig.getParameter<std::string>("FolderName") )
+ , metToken_ ( consumes<reco::PFMETCollection> (iConfig.getParameter<edm::InputTag>("met") ) )
+ , jetToken_ ( mayConsume<reco::PFJetCollection> (iConfig.getParameter<edm::InputTag>("jets") ) )
+ , eleToken_ ( mayConsume<reco::GsfElectronCollection>(iConfig.getParameter<edm::InputTag>("electrons") ) )
+ , muoToken_ ( mayConsume<reco::MuonCollection> (iConfig.getParameter<edm::InputTag>("muons") ) )
+ , vtxToken_ ( mayConsume<reco::VertexCollection> (iConfig.getParameter<edm::InputTag>("vertices") ) )
+ , ht_variable_binning_ ( iConfig.getParameter<edm::ParameterSet>("histoPSet").getParameter<std::vector<double> >("htBinning") )
+ , ht_binning_ ( getHistoPSet (iConfig.getParameter<edm::ParameterSet>("histoPSet").getParameter<edm::ParameterSet> ("htPSet") ) )
@mtosi <https://github.com/mtosi> - we (me and @UBParker
<https://github.com/ubparker> ) removed the fixed binning but then we
realised that htvsLS 2D histogram depends on fixed binning, so we changed
the definition of this histogram as - variable binning vs LS 2D histogram (
https://github.com/UBParker/cmssw/blob/AddingHLTEl50PFJet165/
DQMOffline/Trigger/plugins/METMonitor.cc#L117-#L126). I think the
compilation error is coming because its not defined in the header (.h)
file. After adding that in the .h file, I am trying to compile it locally
but now I see that kind of format is not defined in the
DQMServices/Core/interface/DQMStore.h file. So can we just keep the fixed
binning definition for the htvsLS plot and also similarly for the metvsLS
plot.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19407 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEt58_BtAQnjIfU-dSEZzvty0q89A3J5ks5sLJ8igaJpZM4OCib->
.
|
Let's close this PR. I have the necessary changes implemented here: master...rappoccio:EXOB2G_HLTMON_92x_Part3 Once #19178 and #19534 are integrated, I can integrate this on top of them (after a quick rebase). |
Also I have the 92x backport ready, with similar prerequisite PRs: https://github.com/rappoccio/cmssw/tree/EXOB2G_HLTMON_92xbackport_Part3 |
No description provided.