How statement and proof provenance work
The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.
- Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
- AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
- AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.
These labels describe origin, not correctness: citations and verification chips remain separate evidence.
A finite-budget trust-region method with ratio-based radius updates
Definition
Input of class , an initial point ,
an initial radius , a trial cap
, a target , constants
, ,
, and a declared model-Hessian bound . At each
trial , the supplied symmetric model matrix must satisfy
. A finite-budget subproblem routine returns either a
vector or failure; its output is treated only as a candidate and is not
assumed to minimize the trust-region model. The output is the last accepted
point and one of stationary, target-achieved, outer-budget-exhausted,
or model-evaluation-failure.
For , in order:
- Set . If , return . If , return . If , return .
- Form from Quadratic trust-region models and the actual-to-predicted reduction ratio, compute the Cauchy step from The Cauchy step for a quadratic trust-region model, and set . Query with this model and radius. Use its candidate only if it is feasible and ; otherwise set . If it qualifies, set . If , interpret . Whenever , replace the candidate by .
- Recompute . Evaluate . If this evaluation is unavailable, return .
- If , reject: set and . Otherwise accept and set . If and , set ; in every other accepted case set .
The finite subproblem budget alone does not imply convergence or a complexity bound.
Depends on
Used by
Dependency tree · two levels
10 results within two dependency steps of this one, each drawn at its shortest distance from it. An arrow runs from a result to what uses it, so the chart reads left to right and ends at this result, which carries a heavier outline. Every node is a link to that result. Click elsewhere on the chart to enlarge it.
Sources
- Jorge Nocedal and Stephen J. Wright, Numerical Optimization, second edition (standard reference, not scraped)
- Nick Gould, Continuous Optimization Algorithms, Part 3.2: Trust-Region Methods (standard reference, not scraped)