test
CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
L1AnalysisRecoJet.h
Go to the documentation of this file.
1 #ifndef __L1Analysis_L1AnalysisRecoJet_H__
2 #define __L1Analysis_L1AnalysisRecoJet_H__
3 
4 //-------------------------------------------------------------------------------
5 // Created 05/03/2010 - A.C. Le Bihan
6 //
7 //
8 // Original code : L1Trigger/L1TNtuples/L1RecoJetNtupleProducer - Jim Brooke
9 //-------------------------------------------------------------------------------
10 
11 #include "JetMETCorrections/JetCorrector/interface/JetCorrector.h"
12 #include "DataFormats/JetReco/interface/CaloJetCollection.h"
13 #include "DataFormats/JetReco/interface/JetID.h"
14 #include "L1AnalysisRecoJetDataFormat.h"
15 
16 #include "FWCore/Framework/interface/Event.h"
17 #include "FWCore/Framework/interface/EventSetup.h"
18 
19 
20 namespace L1Analysis
21 {
22  class L1AnalysisRecoJet
23  {
24  public:
25  L1AnalysisRecoJet();
26  ~L1AnalysisRecoJet();
27 
28  //void Print(std::ostream &os = std::cout) const;
29  void SetCaloJet(const edm::Event& event,
30  const edm::EventSetup& setup,
31  const edm::Handle<reco::CaloJetCollection> caloJets,
32  //edm::Handle<edm::ValueMap<reco::JetID> > jetsID,
33  //edm::Handle<reco::JetCorrector> jetCorrector,
34  unsigned maxJet);
35  L1AnalysisRecoJetDataFormat * getData() {return &recoJet_;}
36  void Reset() {recoJet_.Reset();}
37 
38  private :
39  L1AnalysisRecoJetDataFormat recoJet_;
40  };
41 }
42 #endif
43 
44 
L1Analysis::L1AnalysisRecoJet::SetCaloJet
void SetCaloJet(const edm::Event &event, const edm::EventSetup &setup, const edm::Handle< reco::CaloJetCollection > caloJets, unsigned maxJet)
Definition: L1AnalysisRecoJet.cc:15
L1Analysis::L1AnalysisRecoJet::getData
L1AnalysisRecoJetDataFormat * getData()
Definition: L1AnalysisRecoJet.h:35
L1Analysis::L1AnalysisRecoJet::recoJet_
L1AnalysisRecoJetDataFormat recoJet_
Definition: L1AnalysisRecoJet.h:39
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