1 #ifndef DTCHAMBEREFFICIENCY_H
2 #define DTCHAMBEREFFICIENCY_H
116 #endif // DTANALYZER_H
MuonDetLayerMeasurements * theMeasurementExtractor
edm::ESHandle< GlobalTrackingGeometry > theTrackingGeometry
edm::ESHandle< DTGeometry > dtGeom
MuonServiceProxy * theService
edm::InputTag thecscSegments
std::vector< std::vector< MonitorElement * > > histosPerW
DTChamberEfficiency(const edm::ParameterSet &pset)
edm::InputTag labelRPCRecHits
std::string theNavigationType
std::vector< const DetLayer * > compatibleLayers(const DetLayer *initialLayer, const FreeTrajectoryState &fts, PropagationDirection propDir)
edm::InputTag thedt4DSegments
bool chamberSelection(const DetId &idDetLay, reco::TransientTrack &trans_track) const
edm::ESHandle< Propagator > propagator() const
edm::InputTag theTracksLabel
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::ESHandle< MagneticField > magfield
void beginRun(const edm::Run &, const edm::EventSetup &)
MeasurementContainer segQualityCut(const MeasurementContainer seg_list) const
std::vector< TrajectoryMeasurement > MeasurementContainer
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
Chi2MeasurementEstimator * theEstimator