1 #ifndef L1Trigger_RPCTrigger_MuonsGrabber_h
2 #define L1Trigger_RPCTrigger_MuonsGrabber_h
36 #include <xercesc/dom/DOM.hpp>
75 std::vector< RPCMuonExtraStruct >
m_muons;
80 XERCES_CPP_NAMESPACE::DOMImplementation*
m_dom;
81 XERCES_CPP_NAMESPACE::DOMDocument*
m_doc;
XERCES_CPP_NAMESPACE::DOMImplementation * m_dom
FWCore Framework interface EventSetupRecordImplementation h
Helper function to determine trigger accepts.
std::string IntToString(int i)
static MuonsGrabber & Instance()
void setRPCBasicTrigConfig(RPCBasicTrigConfig *c)
const MuonsGrabber & operator=(const MuonsGrabber &)
void startNewEvent(int event, int bx)
RPCBasicTrigConfig * m_trigConfig
XERCES_CPP_NAMESPACE::DOMElement * m_rootElem
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
XERCES_CPP_NAMESPACE::DOMDocument * m_doc
std::vector< RPCMuonExtraStruct > m_muons
XERCES_CPP_NAMESPACE::DOMElement * m_currEvent
void addMuon(RPCTBMuon &mu, int lvl, int region, int hs, int index)
void writeDataForRelativeBX(int bx)