CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
EventSkipperByID.h
Go to the documentation of this file.
1 #ifndef FWCore_Sources_EventSkipperByID_h
2 #define FWCore_Sources_EventSkipperByID_h
3 
8 #include <memory>
9 #include <vector>
10 
11 namespace edm {
12  class ParameterSet;
14 
16  public:
17  explicit EventSkipperByID(ParameterSet const& pset);
20  bool skippingLumis() const {return skippingLumis_;}
21  bool skippingEvents() const {return skippingEvents_;}
22  bool somethingToSkip() const {return somethingToSkip_;}
23  static
24  std::auto_ptr<EventSkipperByID>create(ParameterSet const& pset);
25  static void fillDescription(ParameterSetDescription & desc);
26 
27  private:
28 
32  std::vector<LuminosityBlockRange> whichLumisToSkip_;
33  std::vector<LuminosityBlockRange> whichLumisToProcess_;
34  std::vector<EventRange> whichEventsToSkip_;
35  std::vector<EventRange> whichEventsToProcess_;
39  };
40 }
41 
42 #endif
unsigned int EventNumber_t
Definition: EventRange.h:30
bool skippingLumis() const
tuple lumi
Definition: fjr2json.py:35
bool skipIt(RunNumber_t run, LuminosityBlockNumber_t lumi, EventNumber_t event) const
LuminosityBlockNumber_t firstLumi_
unsigned int LuminosityBlockNumber_t
bool skippingEvents() const
std::vector< LuminosityBlockRange > whichLumisToSkip_
std::vector< EventRange > whichEventsToProcess_
std::vector< LuminosityBlockRange > whichLumisToProcess_
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
std::vector< EventRange > whichEventsToSkip_
EventNumber_t firstEvent_
static void fillDescription(ParameterSetDescription &desc)
bool somethingToSkip() const
unsigned int RunNumber_t
Definition: EventRange.h:32
static std::auto_ptr< EventSkipperByID > create(ParameterSet const &pset)
EventSkipperByID(ParameterSet const &pset)