1 #ifndef Validation_MuonDTDigis_h
2 #define Validation_MuonDTDigis_h
35 #include "SimMuon/DTDigitizer/test/Histograms.h"
73 typedef std::map<DTWireId, std::vector<const PSimHit*> >
DTWireIdMap;
MonitorElement * meDoubleDigi_
MonitorElement * meWire_DoubleDigi_
std::vector< MonitorElement * > meDigiTimeBox_SL_
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
MonitorElement * meDigiHisto_
std::map< DTWireId, std::vector< const PSimHit * > > DTWireIdMap
MonitorElement * meMB2_digi_occup_
MonitorElement * meMB3_sim_occup_
MonitorElement * meDigiEfficiencyMu_
MonitorElement * meDigiTimeBox_wheel2m_
MonitorElement * meDigiTimeBox_wheel1m_
MonitorElement * meDigiTimeBox_wheel0_
MonitorElement * meMB4_sim_occup_
MonitorElement * meMB1_sim_occup_
MonitorElement * meMB2_sim_occup_
MonitorElement * meMB3_digi_occup_
MonitorElement * meDigiTimeBox_
MonitorElement * meDigiTimeBox_wheel1p_
MonitorElement * meMB4_digi_occup_
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
hDigis * WheelHistos(int wheel)
MonitorElement * meSimvsDigi_
MonitorElement * meDigiEfficiency_
MonitorElement * meDigiTimeBox_wheel2p_
MonitorElement * meMB1_digi_occup_
MuonDTDigis(const edm::ParameterSet &pset)