Incorporating Efficiency into Physics Functions

Last Update: 01-Dec-05

Index

  1. Base PDF - without efficiency
  2. Efficiency vs x(meas)
  3. Efficiency vs x(true)
  4. Efficiency in Zero-Lifetime Sources
  5. Implementation in Code - the Efficiency Class

Base PDF without Efficiency

PDF depends on: Without Efficiency correction Source-by-source physics function where P is the function describing the exponential decay or oscillation.

Efficiency vs. x(meas)

Define: ε(xm) = Nisel / Nigen
where Ni = number of events in the bin containing xm.

Gives new PDF:

where Aa is a normalization factor, defined such that the integral of the PDF is one, which will depend on the values of the physics function parameters.

Aa must be re-calculated every time the new physics function, F'a is evaluated, because the parameters might have changed. This will involve another loop over the physics functions and will slow things down terribly.


Efficiency vs. x(true)

Define: ε(xt) = Nisel / Nigen
where Ni = number of events in the bin containing xt.

Gives new PDF:

where now This has the possible benefit of being able to evaluate Aa analytically if a simple functional form can be found for ε(xt) since A is set by the condition: However, this integral has to be coded explicitly for every permutation of physics function, efficiency function and physics function variable which would make the code terrible to maintain.

Efficiency in Zero-Lifetime Sources

x(true)

x(meas) Here there is no nice expression for the physics function, so:

and A has to be recalculated every time F' is evaluated.

Implementation in Code - the Efficiency Class

General
Use eff vs. x(true) as a start.

Multiplies pdf in PDFEvt.

Functions

Class Members

Constructor Parameters