1 #ifndef CommonTools_RecoAlgos_TrackWithVertexSelector_H
2 #define CommonTools_RecoAlgos_TrackWithVertexSelector_H
30 init(iEvent);
return (*
this)(
t);
bool testTrack(const reco::Track &t) const
bool testVertices(const reco::Track &t, const reco::VertexCollection &vtxs) const
reco::VertexCollection const * vcoll_
std::vector< Vertex > VertexCollection
collection of Vertex objects
uint32_t numberOfValidHits_
edm::EDGetTokenT< reco::VertexCollection > vertexToken_
void init(const edm::Event &event, const edm::EventSetup &)
bool operator()(const reco::Track &t) const
~TrackWithVertexSelector()
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
uint32_t numberOfValidPixelHits_
XYZPointD XYZPoint
point in space with cartesian internal representation
bool operator()(const reco::Track &t, const edm::Event &iEvent)
uint32_t numberOfLostHits_
TrackWithVertexSelector(const edm::ParameterSet &iConfig, edm::ConsumesCollector &&iC)