CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
EventHistoryGetter.cc
Go to the documentation of this file.
1 // -*- C++ -*-
2 //
3 // Package: DataFormats
4 // Class : EventHistoryGetter
5 //
6 // Implementation:
7 // [Notes on implementation]
8 //
9 // Original Author:
10 // Created: Wed Feb 10 11:15:18 CST 2010
11 // $Id: EventHistoryGetter.cc,v 1.1 2010/02/12 15:26:08 ewv Exp $
12 //
13 
14 // user include files
16 
17 
18 namespace fwlite {
19 
20  //
21  // constructors and destructor
22  //
24  event_ = event;
25  }
26 
28 
29  //
30  // const member functions
31  //
33  return event_->history();
34  }
35 }
const edm::ProcessHistory & history() const
const fwlite::Event * 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
const edm::ProcessHistory & history() const
Definition: Event.cc:309