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.
Full-memory Bfgs with Wolfe search, descent reset, and Powell damping
Definition
Inputs are a objective on an open with , , consistent SPD matrices with , a reset scale , constants , finite line-search and iteration budgets (zero is allowed), a direction mode exact or rounded-Cholesky, and an update mode undamped or Powell. For rounded-Cholesky mode, also input a finite binary arithmetic format for the called direction procedure.
Initialize , , , , and . If , return stationary at . While , if , return stationary at . Use the Euclidean inner product of The Euclidean inner product on in descent and curvature tests. In exact direction mode set . In rounded-Cholesky mode, first check that every entry of and is finite and representable in the selected format. If any entry is not, return direction-input-failure with . Otherwise call Bfgs Hessian direction by failure-aware Cholesky solve with in that format; if the factorization or triangular solve fails, return its failure status with . Otherwise set to its returned direction. If the computed direction is not descending, reset , , and set .
Call Finite-budget bracketing and zoom for a strong Wolfe step with . If it returns a failure status, return that status and . Otherwise take its positive strong Wolfe step , set , and compute . Define In undamped mode set . In Powell mode put and use the damping rule of Bfgs curvature pairs and Hessian/inverse updates to form . If , skip the matrix update and return curvature-rejected with . Otherwise update both matrices by If any required scalar or matrix operation is undefined, discard partial update results and return update-failure with . After a successful update, commit as the state for the next iteration. If , return stationary at ; if , return iteration-budget-exhausted at . Otherwise set and continue from that committed state. A line-search failure returns its status with . If the loop exits because without another return, return iteration-budget-exhausted with ; this covers . The output is the last point and one of stationary, a line-search status, direction-input-failure, factorization/solve failure, curvature-rejected, update-failure, or iteration-budget-exhausted.
All objective and gradient evaluations, line-search arithmetic, descent and curvature tests, resets, and BFGS matrix updates are exact over . Only the called rounded-Cholesky factorization and triangular solves use the selected finite arithmetic. The representability check is repeated before every call, since exact updates need not preserve representable entries. The rounded-Cholesky direction mode specifies a computed factor-and-solve direction only; this item supplies no backward-error or convergence theorem for that mode. Its returned direction is checked for descent before the strong Wolfe search. The line-search procedure can fail within its finite budgets even when an acceptable step exists.
Depends on
Used by
- An exact Bfgs secant update on a two-variable quadratic Example
- Full-memory and limited-memory storage costs Example
- Powell damping repairs a negative-curvature trial pair Example
- Locally Lipschitz Hessians give the BFGS Dennis–Moré condition Lemma
- Full-memory Bfgs converges globally and linearly on a uniformly strongly convex level set Theorem
- Full-memory Bfgs is locally superlinear when the Hessian is Lipschitz Theorem
Dependency tree · two levels
25 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, 2nd ed. (standard reference, not scraped)
- Manuel Carreira-Perpiñán, Lecture Notes on Numerical Optimization (standard reference, not scraped)