A tolerance-budget residual bound for multiplier bisection controls the physical bias left unused by a numerical allocation, rather than only the numerical error in its Lagrange multiplier. Use from monotonicity of the multiplier equation for capped tolerances. Suppose a positive bracket satisfies . Choosing the upper endpoint gives a feasible allocation, with residual
Choosing the lower endpoint can violate the budget. The direction of monotonicity therefore matters even when both endpoints are numerically close.
For an a priori bound, put . On the entire bracket, each summand obeys Lipschitz continuity with constant at most , including across its breakpoint. Hence
After bisections of an original bracket with , the corresponding worst-case bound is . This is conservative; evaluating the two endpoint budgets can give a much tighter residual certificate.
For an original stopping example, use , and in common normalized bias units. The bracket straddles the root. Its feasible upper endpoint leaves unused. One bisection evaluates and replaces the upper endpoint, reducing that unused amount to about . A residual allowance of is now met, despite a breakpoint lying inside the bracket.
This gives a thresholded stopping of a capped-tolerance multiplier search in the same units as the permitted bias. Floating-point comparisons also need an allowance for rounding if they are to serve as hard certificates. The underlying bias coefficients and cost model remain assumptions of cost-weighted allocation of baseline-response tolerances; numerical precision cannot validate missing physical terms. NIST's pulse-radiometer account motivates the offset/leakage constraints rather than prescribing this numerical stopping rule.[ref]
Thresholded stopping of a capped-tolerance multiplier search ends a numerical allocation when a feasible physical budget is sufficiently well used. With the decreasing budget function in tolerance-budget residual bound for multiplier bisection, an exact upper bracket endpoint satisfies . A residual requirement is , where has the same physical units as the permitted deterministic bias . A small change in alone does not establish that condition.
Numerical evaluation also needs a bound. Suppose the reported value has validated absolute error . Both feasibility and the residual requirement are certified if
Equivalently, the acceptable reported value lies in
This window is empty if . Iterating the multiplier more accurately cannot by itself overcome an evaluation-error bound larger than the desired physical certificate.
For an original numerical certificate, let , and . Values are certifiable. A reported places the actual budget in , so it is feasible and leaves at most unused. A reported is closer to ten but could represent and therefore does not certify feasibility.
The evaluation allowance must itself be justified, for example by validated arithmetic or an explicit forward-error analysis. Uncertain physical coefficients also need their stipulated worst-case bounds before the numerical sum can certify the physical error. NIST's pulse-radiometer discussion motivates the offset and leakage terms; it does not provide the hypothetical numerical tolerances above.[ref]

Articles by others on the same topic (0)

There are currently no matching articles.