CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
GPFGenParticle.h
Go to the documentation of this file.
1 #ifndef Graphic_GenParticle_h
2 #define Graphic_GenParticle_h
3 
9 #include <string>
11 #include "TMarker.h"
12 #include "TLatex.h"
13 #include "TLine.h"
14 
15 class GPFGenParticle : public GPFBase, public TMarker, public TLatex {
16  public:
17  GPFGenParticle(DisplayManager *dm, int view, int ident,
18  double eta, double phi, double en, double pt,int barcode,
19  TAttMarker *attm, std::string name,std::string latexName);
20  GPFGenParticle(DisplayManager *dm, int view, int ident,
21  double *eta, double *phi, double en, double pt,
22  int barcode, int barcodeMother,
23  TAttMarker *attm, std::string name,std::string latexName);
24 
25 
26 
27  virtual ~GPFGenParticle() {;}
28 
29  double getEnergy() { return en_;}
30  double getPt() { return pt_;}
31  virtual void draw();
32  void setColor();
33  void setColor(int newcol);
34  void setInitialColor();
35  void setNewStyle();
36  void setNewSize();
37 
38  //overridden ROOT method
39  virtual void Print(); // *MENU*
40  virtual void ExecuteEvent(Int_t event, Int_t px, Int_t py);
41 
42 
43  private:
44  //energy
45  double en_;
46  double pt_;
47  std::string name_;
48  int barcode_;
50  TLine * line_;
51 
52 
53 };
54 #endif
55 
void setInitialColor()
virtual void draw()
T eta() const
GPFGenParticle(DisplayManager *dm, int view, int ident, double eta, double phi, double en, double pt, int barcode, TAttMarker *attm, std::string name, std::string latexName)
double getEnergy()
std::string name_
virtual void ExecuteEvent(Int_t event, Int_t px, Int_t py)
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
virtual void Print()
virtual ~GPFGenParticle()
Definition: DDAxes.h:10