1 #ifndef RecoParticleFlow_PFRootEvent_ResidualFitter_h
2 #define RecoParticleFlow_PFRootEvent_ResidualFitter_h
18 int nbinsx,
double xlow,
double xup,
19 int nbinsy,
double ylow,
double yup,
20 int nbinsz,
double zlow,
double zup);
39 void Fit(
int x,
int y,
const char* opt=
"");
40 void ShowFit(TH2* h2d,
double x,
double y);
71 std::vector< ResidualFitter::Point >
true_;
72 std::vector< ResidualFitter::Point >
meas_;
void Fit(int x, int y, const char *opt="")
ResidualFitter(const char *name, const char *title, int nbinsx, double xlow, double xup, int nbinsy, double ylow, double yup, int nbinsz, double zlow, double zup)
Point(double x, double y, double z)
static void SetCanvas(int x, int y)
void ExecuteEvent(Int_t event, Int_t px, Int_t py, TObject *sel)
void AddMeas(double x, double y, double z)
void FitSlicesZ(TF1 *f1=0)
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
std::vector< ResidualFitter::Point > true_
void SetFitOptions(const char *opt)
std::vector< ResidualFitter::Point > meas_
void AddTrue(double x, double y, double z)
void SetFitFunction(TF1 *func)
void ShowFit(TH2 *h2d, double x, double y)