1 #ifndef CosmicRegionalSeedGenerator_h
2 #define CosmicRegionalSeedGenerator_h
22 #include "../interface/CosmicTrackingRegion.h"
32 #include "Math/GenVector/VectorUtil.h"
33 #include "Math/GenVector/PxPyPzE4D.h"
edm::EDGetTokenT< reco::TrackCollection > recoTrackMuonsToken_
edm::ParameterSet regionPSet
virtual ~CosmicRegionalSeedGenerator()
bool doJetsExclusionCheck_
edm::EDGetTokenT< reco::CaloJetCollection > recoCaloJetsToken_
double deltaRExclusionSize_
edm::InputTag recoL2MuonsCollection_
edm::InputTag recoTrackMuonsCollection_
edm::EDGetTokenT< reco::MuonCollection > recoMuonsToken_
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::EDGetTokenT< MeasurementTrackerEvent > measurementTrackerEventToken_
std::string thePropagatorName_
edm::InputTag recoMuonsCollection_
virtual std::vector< TrackingRegion * > regions(const edm::Event &event, const edm::EventSetup &es) const
edm::EDGetTokenT< reco::RecoChargedCandidateCollection > recoL2MuonsToken_
CosmicRegionalSeedGenerator(const edm::ParameterSet &conf, edm::ConsumesCollector &&iC)
edm::InputTag recoCaloJetsCollection_