Finite-calibration guards for reciprocal endpoint randomization
ID: finite-calibration-guards-for-reciprocal-endpoint-randomization
Finite-calibration guards for reciprocal endpoint randomization must specify both a valid endpoint decision and how calibration uncertainty enters its probability guarantee. An arbitrary positive floor avoids division by zero but does not establish nominal inclusion, as the example in near-zero probability estimates in reciprocal plug-in rules demonstrates.
One finite-sample construction uses an upper confidence bound for the atom probability , based on independent calibration count . Supposewhere is a calibration failure budget. An exact one-sided binomial bound can be obtained by inversion: for , choose satisfying , and put . This is a confidence statement over calibration samples, not a posterior probability for a fixed after observing one count. The pinned reference documents the exact binomial proportion-interval method.[ref]
SciPy 1.16.2 documentation. BinomTestResult.proportion_ci, confidence_level, exact method and returned bounds
For a fixed upper duration endpoint with actual cumulative probability , setThe rule is defined and . On the event , its conditional included probability is . This calculation also requires independence of the calibration, future duration and auxiliary endpoint draw as stipulated by the parent model.
For an original zero-count example, take and . Since , inversion gives . With , , and stipulated true , the zero-count conditional included probability is approximately . The bound is much larger than the raw estimate zero, reflecting the uncertainty of a small calibration sample rather than inventing a measured atom fraction.
The calibration confidence level is not free. Since included probabilities are nonnegative even on the failure event, a general joint guarantee from this argument is onlyAt conditional target and calibration confidence , this lower guarantee is , not . To certify an unconditional target using this argument, the conditional target must be at least , provided it can fit below , or the failure budget must be reduced. Any upper-endpoint model error also needs separate accounting.
New to topics? Read the docs here!