CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
EntryFinder.h
Go to the documentation of this file.
1 #ifndef DataFormats_FWLite_EntryFinder_h
2 #define DataFormats_FWLite_EntryFinder_h
3 // -*- C++ -*-
4 //
5 // Package: FWLite/DataFormats
6 // Class : EntryFinder
7 //
16 //
17 // Original Author: Bill Tanenbaum
18 //
19 #if !defined(__CINT__) && !defined(__MAKECINT__)
20 // system include files
21 
22 // user include files
25 
26 // forward declarations
27 
28 namespace fwlite {
29  class BranchMapReader;
30  class EntryFinder {
31  public:
32  EntryFinder();
33  ~EntryFinder();
35  bool empty() const {return indexIntoFile_.empty() && fileIndex_.empty();}
39  void fillIndex(BranchMapReader const& branchMap);
40  static EntryNumber_t const invalidEntry = -1LL;
41  private:
44  };
45 }
46 #endif /*__CINT__ */
47 #endif
unsigned int EventNumber_t
Definition: EventRange.h:30
tuple lumi
Definition: fjr2json.py:35
bool empty() const
True if no runs, lumis, or events are in the file.
edm::IndexIntoFile indexIntoFile_
Definition: EntryFinder.h:42
unsigned int LuminosityBlockNumber_t
long long EntryNumber_t
EntryNumber_t findEvent(edm::RunNumber_t const &run, edm::LuminosityBlockNumber_t const &lumi, edm::EventNumber_t const &event) const
Definition: EntryFinder.cc:57
bool empty() const
Definition: FileIndex.h:112
edm::IndexIntoFile::EntryNumber_t EntryNumber_t
Definition: EntryFinder.h:34
void fillIndex(BranchMapReader const &branchMap)
Definition: EntryFinder.cc:108
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
EntryNumber_t findRun(edm::RunNumber_t const &run) const
Definition: EntryFinder.cc:91
static EntryNumber_t const invalidEntry
Definition: EntryFinder.h:40
bool empty() const
Definition: EntryFinder.h:35
edm::FileIndex fileIndex_
Definition: EntryFinder.h:43
unsigned int RunNumber_t
Definition: EventRange.h:32
EntryNumber_t findLumi(edm::RunNumber_t const &run, edm::LuminosityBlockNumber_t const &lumi) const
Definition: EntryFinder.cc:74