CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
GsfElectronCoreBaseProducer.h
Go to the documentation of this file.
1 #ifndef GsfElectronCoreBaseProducer_h
2 #define GsfElectronCoreBaseProducer_h
3 
4 //
5 // Package: RecoEgamma/EgammaElectronProducers
6 // Class: GsfElectronCoreBaseProducer
7 //
8 // Description:
9 
10 
14 
15 namespace reco
16  {
17  class GsfElectronCore ;
18  }
19 
20 namespace edm
21  {
22  class ParameterSet ;
24  }
25 
30 
32  {
33  public:
34 
36 
39 
40 
41  protected:
42 
43  // to be called by derived producers at the beginning of each new event
44  void initEvent( edm::Event & event, const edm::EventSetup & setup ) ;
49 
51 
52  private:
53 
57 
58  // From Puneeth Kalavase : returns the CTF track that has the highest fraction
59  // of shared hits in Pixels and the inner strip tracker with the electron Track
60  std::pair<reco::TrackRef,float> getCtfTrackRef
61  ( const reco::GsfTrackRef & ) ;
62 
63  } ;
64 
65 
66 #endif
void initEvent(edm::Event &event, const edm::EventSetup &setup)
GsfElectronCoreBaseProducer(const edm::ParameterSet &conf)
edm::Handle< reco::TrackCollection > ctfTracksH_
edm::Handle< reco::GsfTrackCollection > gsfTracksH_
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
edm::EDGetTokenT< reco::TrackCollection > ctfTracksTag_
tuple conf
Definition: dbtoconf.py:185
edm::EDGetTokenT< reco::GsfPFRecTrackCollection > gsfPfRecTracksTag_
std::pair< reco::TrackRef, float > getCtfTrackRef(const reco::GsfTrackRef &)
static void fillDescription(edm::ParameterSetDescription &)
edm::Handle< reco::GsfPFRecTrackCollection > gsfPfRecTracksH_
void fillElectronCore(reco::GsfElectronCore *)
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")
edm::EDGetTokenT< reco::GsfTrackCollection > gsfTracksTag_