1 #ifndef MuonSeedGenerator_SETPatternRecognition_h
2 #define MuonSeedGenerator_SETPatternRecognition_h
21 std::vector<MuonRecHitContainer> &
result);
28 const double&
chi2,
const int& ndf);
edm::EDGetTokenT< DTRecSegment4DCollection > dtToken
edm::EDGetTokenT< RPCRecHitCollection > rpcToken
edm::EDGetTokenT< CSCSegmentCollection > cscToken
double minLocalSegmentAngle
edm::InputTag CSCRecSegmentLabel
virtual ~SETPatternRecognition()
double outsideChamberErrorScale
bool segmentCleaning(const DetId &detId, const LocalPoint &localPosition, const LocalError &localError, const LocalVector &localDirection, const LocalError &localDirectionError, const double &chi2, const int &ndf)
void setServiceProxy(MuonServiceProxy *service)
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
MuonServiceProxy * theService
edm::InputTag DTRecSegmentLabel
SETPatternRecognition(const edm::ParameterSet &pset, edm::ConsumesCollector &iC)
virtual void produce(const edm::Event &event, const edm::EventSetup &eSetup, std::vector< MuonRecHitContainer > &result)
edm::InputTag RPCRecSegmentLabel