CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
MuonSeedMerger.cc
Go to the documentation of this file.
2 
14 // Framework
19 
20 // Data Formats
24 
25 using namespace std;
26 using namespace edm;
27 
29  const string metname = "Muon|RecoMuon|MuonSeedMerger";
30 
31  theSeedCollectionLabels = parameterSet.getParameter<vector<InputTag> >("SeedCollections");
32 
33  LogTrace(metname)<< "MuonSeedMerger will Merge the following seed collections:";
34  for(vector<InputTag>::const_iterator label = theSeedCollectionLabels.begin();
35  label != theSeedCollectionLabels.end(); ++label)
36  LogTrace(metname) << *label;
37 
38 
39  produces<TrajectorySeedCollection>();
40 }
41 
42 
44 
45 void MuonSeedMerger::produce(Event& event, const EventSetup& eventSetup){
46 
47  const string metname = "Muon|RecoMuon|MuonSeedMerger";
48 
49  std::auto_ptr<TrajectorySeedCollection> output(new TrajectorySeedCollection());
50 
52 
53  for(vector<InputTag>::const_iterator label = theSeedCollectionLabels.begin();
54  label != theSeedCollectionLabels.end(); ++label){
55  event.getByLabel(*label,seeds);
56  LogTrace(metname) << *label << " has "<< seeds->size() <<" seeds";
57  for(View<TrajectorySeed>::const_iterator seed = seeds->begin(); seed != seeds->end(); ++seed)
58  output->push_back(*seed);
59  }
60 
61  event.put(output);
62 }
T getParameter(std::string const &) const
boost::indirect_iterator< typename seq_t::const_iterator > const_iterator
Definition: View.h:81
const std::string metname
MuonSeedMerger(const edm::ParameterSet &)
Constructor.
virtual void produce(edm::Event &, const edm::EventSetup &)
std::vector< TrajectorySeed > TrajectorySeedCollection
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
#define LogTrace(id)
virtual ~MuonSeedMerger()
Destructor.