CMS 3D CMS Logo

TrackerSeedGenerator.cc
Go to the documentation of this file.
3 
5 
7 
9  const TrackingRegion& region,
10  const TrackerTopology* tTopo,
13  run(result, *theEvent, es, region);
14  return;
15 }
TrackerSeedGenerator::init
virtual void init(const MuonServiceProxy *service)
Definition: TrackerSeedGenerator.cc:6
TrackerSeedGenerator::TrackCand
std::pair< const Trajectory *, reco::TrackRef > TrackCand
Definition: TrackerSeedGenerator.h:30
service
Definition: service.py:1
TrackerSeedGenerator::setEvent
virtual void setEvent(const edm::Event &)
Definition: TrackerSeedGenerator.cc:16
TrackerTopology
Definition: TrackerTopology.h:16
TrackerSeedGenerator.h
TrackerSeedGenerator::theProxyService
const MuonServiceProxy * theProxyService
Definition: TrackerSeedGenerator.h:51
TrackerTopology.h
TrackerSeedGenerator::BTSeedCollection
std::vector< TrajectorySeed > BTSeedCollection
Definition: TrackerSeedGenerator.h:26
TrackerSeedGenerator::theEvent
const edm::Event * theEvent
Definition: TrackerSeedGenerator.h:50
TrackerSeedGenerator::run
virtual void run(TrajectorySeedCollection &seeds, const edm::Event &ev, const edm::EventSetup &es, const TrackingRegion &region)
Definition: TrackerSeedGenerator.h:44
MuonServiceProxy::eventSetup
const edm::EventSetup & eventSetup() const
Definition: MuonServiceProxy.h:76
edm::EventSetup
Definition: EventSetup.h:57
TrackerSeedGenerator::trackerSeeds
virtual void trackerSeeds(const TrackCand &, const TrackingRegion &, const TrackerTopology *, BTSeedCollection &)
Definition: TrackerSeedGenerator.cc:8
timingPdfMaker.can
can
Definition: timingPdfMaker.py:311
MuonServiceProxy.h
HLT_2018_cff.region
region
Definition: HLT_2018_cff.py:81479
TrackingRegion
Definition: TrackingRegion.h:40
mps_fire.result
result
Definition: mps_fire.py:303
MuonServiceProxy
Definition: MuonServiceProxy.h:38
event
Definition: event.py:1
edm::Event
Definition: Event.h:73
event
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