CMS 3D CMS Logo

FWFFNavigator.cc
Go to the documentation of this file.
2 #include "TSystem.h"
3 
6  gSystem->ExitLoop();
7 }
8 
11  gSystem->ExitLoop();
12 }
13 
16  gSystem->ExitLoop();
17 }
18 
21  gSystem->ExitLoop();
22 }
23 
32  newEvent_.emit();
33 }
34 
FWFFNavigator::lastEvent
void lastEvent() override
Definition: FWFFNavigator.cc:19
FWFFNavigator.h
FWFFNavigator::setCurrentEvent
void setCurrentEvent(const edm::Event *)
Definition: FWFFNavigator.cc:28
FWNavigatorBase::newEvent_
sigc::signal< void > newEvent_
Definition: FWNavigatorBase.h:56
FWFFNavigator::firstEvent
void firstEvent() override
Definition: FWFFNavigator.cc:14
FWFFNavigator::kFirstEvent
Definition: FWFFNavigator.h:13
FWFFNavigator::m_currentEvent
const edm::Event * m_currentEvent
Definition: FWFFNavigator.h:59
FWFFNavigator::kPreviousEvent
Definition: FWFFNavigator.h:13
FWFFNavigator::nextEvent
void nextEvent() override
Definition: FWFFNavigator.cc:4
FWFFNavigator::m_currentTransition
enum FWFFNavigatorState m_currentTransition
Definition: FWFFNavigator.h:61
FWFFNavigator::previousEvent
void previousEvent() override
Definition: FWFFNavigator.cc:9
edm::EventBase::id
edm::EventID id() const
Definition: EventBase.h:59
FWFFNavigator::kNextEvent
Definition: FWFFNavigator.h:13
FWFFNavigator::m_firstEventID
edm::EventID m_firstEventID
Definition: FWFFNavigator.h:60
FWFFNavigator::kLastEvent
Definition: FWFFNavigator.h:13
FWFFNavigator::getFirstEventID
const edm::EventID & getFirstEventID()
Definition: FWFFNavigator.cc:35
event
Definition: event.py:1
edm::EventID
Definition: EventID.h:31
edm::Event
Definition: Event.h:73
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