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
Exo trigger prompt monitoring92 x #18971
Exo trigger prompt monitoring92 x #18971
Conversation
A new Pull Request was created by @gomber for master. It involves the following packages: Calibration/HcalAlCaRecoProducers @ghellwig, @arunhep, @cerminar, @dmitrijus, @cmsbuild, @franzoni, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
histname = "photon_eta"; histtitle = "Photon eta"; | ||
bookME(ibooker,photonEtaME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax); | ||
setTitle(photonEtaME_,"Photon #eta","events / 0.1"); | ||
|
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.
aren't you missing the 2D plot ?
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.
which 2D plots you want? i am just making trigger efficiency plot as a function of pt, eta and phi, so that should be enough
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.
in addition, are you planning to add variables for the "out-of-time" photon ?
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 mean having eta and phi 1D plot is sufficient. And yes we would like to add out-of-time photons variable for displaced photons, but later.
#HLT_SinglePhoton200_IDTight | ||
SinglePhoton300_monitoring = hltPhotonmonitoring.clone() | ||
SinglePhoton300_monitoring.FolderName = cms.string('HLT/Photon/Photon300/') | ||
SinglePhoton300_monitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_Photon300_NoHE_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.
aren't you apply any offline selection ?
# HLT_SinglePhoton175_IDTight | ||
SinglePhoton175_monitoring = hltPhotonmonitoring.clone() | ||
SinglePhoton175_monitoring.FolderName = cms.string('HLT/Photon/Photon175/') | ||
SinglePhoton175_monitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_Photon175_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.
aren't you apply any offline 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.
there is photonselection in the python file photonMonitoring_cfi, which will be created from .cc file.
desc.addstd::string("photonSelection", "pt > 145 && eta<1.4442 && hadTowOverEm<0.0597 && full5x5_sigmaIetaIeta()<0.01031 && chargedHadronIso<1.295");
efficiency in the eta-phi plane ;)
mia
…On Fri, May 26, 2017 at 8:37 PM, gomber ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In DQMOffline/Trigger/plugins/PhotonMonitor.cc
<#18971 (comment)>:
> + bookME(ibooker,photonME_variableBinning_,histname,histtitle,photon_variable_binning_);
+ setTitle(photonME_variableBinning_,"Photon pT [GeV]","events / [GeV]");
+
+ histname = "photonVsLS"; histtitle = "photon pt vs LS";
+ bookME(ibooker,photonVsLS_,histname,histtitle,ls_binning_.nbins, ls_binning_.xmin, ls_binning_.xmax,photon_binning_.xmin, photon_binning_.xmax);
+ setTitle(photonVsLS_,"LS","Photon pT [GeV]");
+
+ histname = "photon_phi"; histtitle = "Photon phi";
+ bookME(ibooker,photonPhiME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax);
+ setTitle(photonPhiME_,"Photon #phi","events / 0.1 rad");
+
+
+ histname = "photon_eta"; histtitle = "Photon eta";
+ bookME(ibooker,photonEtaME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax);
+ setTitle(photonEtaME_,"Photon #eta","events / 0.1");
+
which 2D plots you want? i am just making trigger efficiency plot as a
function of pt, eta and phi, so that should be enough
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18971 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEt58wA29CzAZl9O6anrutNFRI-5yEdFks5r9xvrgaJpZM4Nn66Y>
.
|
i think this PR needs rebase. |
Pull request #18971 was updated. @ghellwig, @arunhep, @cerminar, @dmitrijus, @cmsbuild, @franzoni, @vanbesien, @davidlange6 can you please check and sign again. |
ea01396
to
65b8733
Compare
Pull request #18971 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again. |
@arunhep should be fine now.. |
So guys, I am adding 2D plot and will do another commit as Mia suggested and then we would be good to go! |
|
||
|
||
histname = "photon_eta"; histtitle = "Photon eta"; | ||
bookME(ibooker,photonEtaME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax); |
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.
shouldn't be eta_binning ?
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.
phi_binning which we are using in the code is very general, and can be used for eta too, its 64 bins between -3.2 to 3.2, thats why used the same variable
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.
Ok I am using the following one now, since we are mainly interested in barrel region for these, so looking at the ECAL tower size, 1.4442/0.087 = ~17 bins, so I will cover -1.4442 to 1.4442 with 34 bins.
fillHistoPSetDescription(metPSet); | ||
histoPSet.add<edm::ParameterSetDescription>("photonPSet", metPSet); | ||
std::vector<double> bins = {0.,20.,40.,60.,80.,90.,100.,110.,120.,130.,140.,150.,160.,170.,180.,190.,200.,220.,240.,260.,280.,300.,350.,400.,450.,1000.}; | ||
histoPSet.add<std::vector<double> >("photonBinning", bins); |
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 think you should overwrite this in the python config
taking into account the expected turnON
please use the more appropriate for photon obj
thanks
mia
…On Fri, May 26, 2017 at 9:52 PM, gomber ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In DQMOffline/Trigger/plugins/PhotonMonitor.cc
<#18971 (comment)>:
> +
+ histname = "photon_pt_variable"; histtitle = "photon PT";
+ bookME(ibooker,photonME_variableBinning_,histname,histtitle,photon_variable_binning_);
+ setTitle(photonME_variableBinning_,"Photon pT [GeV]","events / [GeV]");
+
+ histname = "photonVsLS"; histtitle = "photon pt vs LS";
+ bookME(ibooker,photonVsLS_,histname,histtitle,ls_binning_.nbins, ls_binning_.xmin, ls_binning_.xmax,photon_binning_.xmin, photon_binning_.xmax);
+ setTitle(photonVsLS_,"LS","Photon pT [GeV]");
+
+ histname = "photon_phi"; histtitle = "Photon phi";
+ bookME(ibooker,photonPhiME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax);
+ setTitle(photonPhiME_,"Photon #phi","events / 0.1 rad");
+
+
+ histname = "photon_eta"; histtitle = "Photon eta";
+ bookME(ibooker,photonEtaME_,histname,histtitle, phi_binning_1.nbins, phi_binning_1.xmin, phi_binning_1.xmax);
phi_binning which we are using in the code is very general, and can be
used for eta too, its 64 bins between -3.2 to 3.2, thats why used the same
variable
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18971 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEt582Eadk-RrjLO2v4U4KsIw5-ym2VRks5r9y17gaJpZM4Nn66Y>
.
|
photonME_variableBinning_.denominator = nullptr; | ||
photonVsLS_.numerator = nullptr; | ||
photonVsLS_.denominator = nullptr; | ||
photonEtaME_.numerator = nullptr; |
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 think the variable binning should be used for eta 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.
are you going to add the variable binning for properly handle the ECAL geometry ?
photonEtaME_.denominator = nullptr; | ||
photonPhiME_.numerator = nullptr; | ||
photonPhiME_.denominator = nullptr; | ||
|
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 would suggest to add the 2D plot
and H/E and probably R9
Photon60_monitoring = hltPhotonmonitoring.clone() | ||
Photon60_monitoring.FolderName = cms.string('HLT/Photon/Photon60/') | ||
Photon60_monitoring.denGenericTriggerEventPSet.hltPaths = cms.vstring() | ||
Photon60_monitoring.numGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_Photon60_R9Id90_CaloIdL_IsoL_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.
are you sure it is available in 2017 ?
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.
yes it is available kevin requested them
https://its.cern.ch/jira/browse/CMSHLT-1327
|
||
Photon60_DisplacedIdL_PFJet350MinPFJet15_monitoring = Photon60_DisplacedIdL_monitoring.clone() | ||
Photon60_DisplacedIdL_PFJet350MinPFJet15_monitoring.FolderName = cms.string('HLT/Photon/Photon60_DisplacedIdL_PFJet350MinPFJet15/') | ||
Photon60_DisplacedIdL_PFJet350MinPFJet15_monitoring.denGenericTriggerEventPSet.hltPaths = cms.vstring("HLT_Photon60_R9Id90_CaloIdL_IsoL_v*","HLT_PFHT350MinPFJet15_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.
are you sure they are available ?
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.
see previous message
what about |
Hi Mia, who requested these paths, I didn't see it in Sam mails, may be I missed it? Regards |
We need monitoring for all triggers. |
Pull request #18971 was updated. @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @vanbesien, @davidlange6 can you please check and sign again. |
@dmitrijus please test again, there was one small bug in the photon_cff file, which i fixed, looks like some typo happened in the last round. |
@davidlange6 Regarding the number of bins, we have 16 histograms which corresponds to 2900 bins in total and then there are 10 instances of it, so that would mean in total this code would add 29000 bins, if this is the kind of information you asked me. |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@davidlange6 Could you please proceed with this? as all the tests are passed and we also provide nbins information? |
all that happened a few hours ago:) |
merge |
This PR includes a backport of the following PRs: - cms-sw#18172 - cms-sw#18950 - cms-sw#18959 - cms-sw#18968 - cms-sw#18971 - cms-sw#19023 - cms-sw#19046 - cms-sw#19078 - cms-sw#19119 - cms-sw#19178 - cms-sw#19290 - cms-sw#19293 - cms-sw#19294 - cms-sw#19490 - cms-sw#19499 - cms-sw#19577 - cms-sw#19585 - cms-sw#19596 - cms-sw#19599 - cms-sw#19627 - cms-sw#19689 - cms-sw#19694 - cms-sw#19703 - cms-sw#19781 - cms-sw#19794 plus the older ones, contained in DQMOffline/Trigger and HLTriggerOffline. It synchronises with CMSSW_9_3_X - DQMServices/ClientConfig - DQMOffline/Configuration - DQMOffline/Trigger - HLTriggerOffline/Btag - HLTriggerOffline/Higgs - HLTriggerOffline/SUSYBSM - HLTriggerOffline/Tau - HLTriggerOffline/Top
This PR includes a backport of the following PRs: - cms-sw#18172 - cms-sw#18950 - cms-sw#18959 - cms-sw#18968 - cms-sw#18971 - cms-sw#19023 - cms-sw#19046 - cms-sw#19078 - cms-sw#19119 - cms-sw#19178 - cms-sw#19290 - cms-sw#19293 - cms-sw#19294 - cms-sw#19490 - cms-sw#19499 - cms-sw#19577 - cms-sw#19585 - cms-sw#19596 - cms-sw#19599 - cms-sw#19627 - cms-sw#19689 - cms-sw#19694 - cms-sw#19703 - cms-sw#19781 - cms-sw#19794 plus the older ones, contained in DQMOffline/Trigger and HLTriggerOffline. It synchronises with CMSSW_9_3_X - DQMServices/ClientConfig - DQMOffline/Configuration - DQMOffline/Trigger - HLTriggerOffline/Btag - HLTriggerOffline/Higgs - HLTriggerOffline/SUSYBSM - HLTriggerOffline/Tau - HLTriggerOffline/Top
This PR includes a backport of the following PRs: - cms-sw#18172 - cms-sw#18950 - cms-sw#18959 - cms-sw#18968 - cms-sw#18971 - cms-sw#19023 - cms-sw#19046 - cms-sw#19078 - cms-sw#19119 - cms-sw#19178 - cms-sw#19290 - cms-sw#19293 - cms-sw#19294 - cms-sw#19490 - cms-sw#19499 - cms-sw#19577 - cms-sw#19585 - cms-sw#19596 - cms-sw#19599 - cms-sw#19627 - cms-sw#19689 - cms-sw#19694 - cms-sw#19703 - cms-sw#19781 - cms-sw#19794 plus the older ones, contained in DQMOffline/Trigger and HLTriggerOffline. It synchronises with CMSSW_9_3_X - DQMServices/ClientConfig - DQMOffline/Configuration - DQMOffline/Trigger - HLTriggerOffline/Btag - HLTriggerOffline/Higgs - HLTriggerOffline/SUSYBSM - HLTriggerOffline/Tau - HLTriggerOffline/Top
No description provided.