CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
PixelClusterSelectorTopBottom.h
Go to the documentation of this file.
1 #ifndef RecoSelectors_PixelClusterSelectorTopBottom_h
2 #define RecoSelectors_PixelClusterSelectorTopBottom_h
3 
4 /* \class PixelClusterSelectorTopBottom
5 *
6 * \author Giuseppe Cerati, INFN
7 *
8 * $Date: 2011/01/14 01:24:51 $
9 * $Revision: 1.2 $
10 *
11 */
12 
14 
19 
21 
29 
31 
32  public:
34  label_( cfg.getParameter<edm::InputTag>( "label" ) ),
35  y_( cfg.getParameter<double>( "y" ) ) { produces<SiPixelClusterCollectionNew>(); }
36 
38 
39  private:
41  double y_;
42 };
43 
44 #endif
void produce(edm::Event &event, const edm::EventSetup &setup)
PixelClusterSelectorTopBottom(const edm::ParameterSet &cfg)
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
void setup(std::vector< TH2F > &depth, std::string name, std::string units="")