CMS 3D CMS Logo
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
List of all members | Public Member Functions | Public Attributes | Static Public Attributes
edm::FileIndex::Element Class Reference

#include <FileIndex.h>

Public Member Functions

 Element ()
 
 Element (RunNumber_t run, LuminosityBlockNumber_t lumi, EventNumber_t event, long long entry)
 
 Element (RunNumber_t run, LuminosityBlockNumber_t lumi, EventNumber_t event)
 
EntryType getEntryType () const
 

Public Attributes

EntryNumber_t entry_
 
EventNumber_t event_
 
LuminosityBlockNumber_t lumi_
 
RunNumber_t run_
 

Static Public Attributes

static EntryNumber_t const invalidEntry = -1LL
 

Detailed Description

Definition at line 32 of file FileIndex.h.

Constructor & Destructor Documentation

edm::FileIndex::Element::Element ( )
inline

Definition at line 35 of file FileIndex.h.

35  : run_(0U), lumi_(0U), event_(0U), entry_(invalidEntry) {
36  }
edm::FileIndex::Element::entry_
EntryNumber_t entry_
Definition: FileIndex.h:50
edm::FileIndex::Element::invalidEntry
static EntryNumber_t const invalidEntry
Definition: FileIndex.h:34
edm::FileIndex::Element::lumi_
LuminosityBlockNumber_t lumi_
Definition: FileIndex.h:48
edm::FileIndex::Element::event_
EventNumber_t event_
Definition: FileIndex.h:49
edm::FileIndex::Element::Element ( RunNumber_t  run,
LuminosityBlockNumber_t  lumi,
EventNumber_t  event,
long long  entry 
)
inline

Definition at line 37 of file FileIndex.h.

References assert(), event_, and lumi_.

37  :
38  run_(run), lumi_(lumi),
39  event_(event), entry_(entry) {
40  assert(lumi_ != 0U || event_ == 0U);
41  }
fjr2json.lumi
tuple lumi
Definition: fjr2json.py:35
assert
assert(m_qm.get())
edm::FileIndex::Element::entry_
EntryNumber_t entry_
Definition: FileIndex.h:50
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
edm::FileIndex::Element::lumi_
LuminosityBlockNumber_t lumi_
Definition: FileIndex.h:48
edm::FileIndex::Element::event_
EventNumber_t event_
Definition: FileIndex.h:49
edm::FileIndex::Element::Element ( RunNumber_t  run,
LuminosityBlockNumber_t  lumi,
EventNumber_t  event 
)
inline

Definition at line 42 of file FileIndex.h.

42  :
43  run_(run), lumi_(lumi), event_(event), entry_(invalidEntry) {}
fjr2json.lumi
tuple lumi
Definition: fjr2json.py:35
edm::FileIndex::Element::entry_
EntryNumber_t entry_
Definition: FileIndex.h:50
edm::FileIndex::Element::invalidEntry
static EntryNumber_t const invalidEntry
Definition: FileIndex.h:34
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
edm::FileIndex::Element::lumi_
LuminosityBlockNumber_t lumi_
Definition: FileIndex.h:48
edm::FileIndex::Element::event_
EventNumber_t event_
Definition: FileIndex.h:49

Member Function Documentation

EntryType edm::FileIndex::Element::getEntryType ( ) const
inline

Definition at line 44 of file FileIndex.h.

References event_, edm::FileIndex::kEvent, edm::FileIndex::kLumi, edm::FileIndex::kRun, and lumi_.

44  {
45  return lumi_ == 0U ? kRun : (event_ == 0U ? kLumi : kEvent);
46  }
edm::FileIndex::Element::lumi_
LuminosityBlockNumber_t lumi_
Definition: FileIndex.h:48
edm::FileIndex::Element::event_
EventNumber_t event_
Definition: FileIndex.h:49

Member Data Documentation

EntryNumber_t edm::FileIndex::Element::entry_

Definition at line 50 of file FileIndex.h.

Referenced by edm::Compare_Run_Lumi_EventEntry::operator()().

EventNumber_t edm::FileIndex::Element::event_

Definition at line 49 of file FileIndex.h.

Referenced by Element(), getEntryType(), edm::Compare_Run_Lumi_EventEntry::operator()(), and edm::operator<().

EntryNumber_t const edm::FileIndex::Element::invalidEntry = -1LL
static

Definition at line 34 of file FileIndex.h.

Referenced by edm::FileIndex::allEventsInEntryOrder().

LuminosityBlockNumber_t edm::FileIndex::Element::lumi_

Definition at line 48 of file FileIndex.h.

Referenced by Element(), getEntryType(), edm::Compare_Run_Lumi_EventEntry::operator()(), and edm::operator<().

RunNumber_t edm::FileIndex::Element::run_

Definition at line 47 of file FileIndex.h.

Referenced by edm::Compare_Run_Lumi_EventEntry::operator()(), and edm::operator<().

Generated for CMSSW Reference Manual by doxygen 1.8.5