CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
TriggerBitChecker.h
Go to the documentation of this file.
1 #ifndef PhysicsTools_Heppy_TriggerBitChecker_h
2 #define PhysicsTools_Heppy_TriggerBitChecker_h
3 
7 #include <vector>
8 #include <string>
9 
10 namespace heppy {
11 
13  public:
14  struct pathStruct {
15  pathStruct( const std::string &s ) : pathName(s), first(0),last(99999999) {}
16  pathStruct() : pathName(), first(0),last(99999999) {}
18  unsigned int first;
19  unsigned int last;
20  };
21 
22  TriggerBitChecker(const std::string &path="DUMMY");
23  TriggerBitChecker(const std::vector<std::string> &paths);
25 
26  bool check(const edm::EventBase &event, const edm::TriggerResults &result) const ;
28 
29  private:
30  // list of path name prefixes
31  std::vector<pathStruct> paths_;
32 
34  mutable std::vector<unsigned int> indices_;
35 
37  void syncIndices(const edm::EventBase &event, const edm::TriggerResults &result) const ;
39 
41  void rmstar() ;
42 };
43 }
44 
45 #endif
void rmstar()
executes a &#39;rm -rf *&#39; in current directory
bool check_unprescaled(const edm::EventBase &event, const edm::TriggerResults &result_tr, const pat::PackedTriggerPrescales &result) const
bool check(const edm::EventBase &event, const edm::TriggerResults &result) const
tuple result
Definition: mps_fire.py:83
std::vector< pathStruct > paths_
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
TriggerBitChecker(const std::string &path="DUMMY")
std::vector< unsigned int > indices_
edm::ParameterSetID lastID_
pathStruct returnPathStruct(const std::string &path) const
void syncIndices(const edm::EventBase &event, const edm::TriggerResults &result) const
sync indices with path names