1 #ifndef Graphic_PFTrack_h
2 #define Graphic_PFTrack_h
19 double pt,TAttMarker *attm,TAttLine *attl, std::string option);
reconstructed track used as an input to particle flow
GPFTrack(DisplayManager *dm, int view, int ident, reco::PFRecTrack *tra, int size, double *x, double *y, double pt, TAttMarker *attm, TAttLine *attl, std::string option)
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 GPFTrack & operator=(const GPFTrack &other)
reco::PFRecTrack * track_
virtual void ExecuteEvent(Int_t event, Int_t px, Int_t py)
tuple size
Write out results.