CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
HcalElectronicsSelector.h
Go to the documentation of this file.
1 #include "MyHcalClasses.h"
2 #include "TObject.h"
3 #include "TCanvas.h"
4 #include "TH2.h"
5 
6 class TCanvas;
7 class TH2;
8 
10 public:
11  class Callbacks {
12  public:
13  virtual ~Callbacks() { }
14  virtual void plot(const MyElectronicsId& id) = 0;
15 
16  };
17 
18  HcalElectronicsSelector(Callbacks* cb,
19  int htrChan_lo=0, int htrChan_hi=24, int fpga_lo=-31, int fpga_hi=31,int crate=0);
20 
21  void fill(const MyElectronicsId& id, double value);
22  void onEvent(int event, int x, int y, TObject *selected);//add crate
23  void Update();
24 private:
26  TCanvas* m_canvas;
27  TH2* m_hist;
28  int m_crate;
29 };
30 
31 
32 
void fill(const MyElectronicsId &id, double value)
virtual void plot(const MyElectronicsId &id)=0
void onEvent(int event, int x, int y, TObject *selected)
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
HcalElectronicsSelector(Callbacks *cb, int htrChan_lo=0, int htrChan_hi=24, int fpga_lo=-31, int fpga_hi=31, int crate=0)