CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
CastorJetIDHelper.h
Go to the documentation of this file.
1 #ifndef RecoJets_JetProducers_interface_CastorJetIDHelper_h
2 #define RecoJets_JetProducers_interface_CastorJetIDHelper_h
3 
4 
5 #include "FWCore/Framework/interface/Frameworkfwd.h"
6 #include "FWCore/Framework/interface/Event.h"
7 #include "DataFormats/JetReco/interface/BasicJet.h"
8 
9 namespace reco {
10 
11  namespace helper {
12 
13  class CastorJetIDHelper {
14 
15  public :
16  // construction
17  CastorJetIDHelper();
18  ~CastorJetIDHelper() {}
19 
20 
21  void initValues ();
22 
23  // interface
24  void calculate( const edm::Event& event, const reco::BasicJet &jet );
25 
26  // member access
27 
28  double emEnergy() const { return emEnergy_;}
29  double hadEnergy() const { return hadEnergy_;}
30  double fem() const { return fem_;}
31  double width() const { return width_;}
32  double depth() const { return depth_;}
33  double fhot() const { return fhot_;}
34  double sigmaz() const { return sigmaz_;}
35  int nTowers() const { return nTowers_;}
36 
37 
38  private:
39 
40 
41  // helper functions
42  double phiangle (double testphi);
43 
44  double emEnergy_;
45  double hadEnergy_;
46  double fem_;
47  double width_;
48  double depth_;
49  double fhot_;
50  double sigmaz_;
51  int nTowers_;
52 
53  static int sanity_checks_left_;
54  };
55  }
56 }
57 #endif
dt_dqm_sourceclient_common_cff.reco
tuple reco
Definition: dt_dqm_sourceclient_common_cff.py:106
reco::BasicJet
Jets made from CaloTowers.
Definition: BasicJet.h:20
reco::helper::CastorJetIDHelper::calculate
void calculate(const edm::Event &event, const reco::BasicJet &jet)
Definition: CastorJetIDHelper.cc:33
reco::helper::CastorJetIDHelper::phiangle
double phiangle(double testphi)
Definition: CastorJetIDHelper.cc:83
event
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger but the state exists so we define the behavior If all triggers are the negative crieriion will lead to accepting the event(this again matches the behavior of"!*"before the partial wildcard feature was incorporated).The per-event"cost"of each negative criterion with multiple relevant triggers is about the same as!*was in the past
Generated for CMSSW Reference Manual by doxygen 1.8.5