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.
Finite-budget Newton and chord solves with scheduled factorization reuse
Definition
Let , let be open, and let be , , residual tolerance , correction budget , and refresh period , . Use the coordinate Jacobian convention of The Jacobian matrix of partial derivatives and the gradient in the scalar-valued case. Since is , A total derivative computes every directional derivative, and its matrix is the Jacobian identifies this Jacobian with the matrix of ; write it as . Residual and Jacobian evaluations, norm comparisons and domain tests are returning primitives; no bound on their internal cost is specified. In chord mode also supply a terminating exact linear-system backend: on each square Jacobian it reports singularity if the matrix is singular, and otherwise returns a retained factor object, and each solve on that object terminates with the exact unique solution for its right-hand side. Factorization and solve work are charged individually. The output is a last valid iterate , a status, and the actual residual norm .
In updated-Newton mode, invoke Finite-budget Newton for a square vector residual with . It recomputes the Jacobian at every correction and returns its stated residual/budget/failure status. Re-evaluate at the returned iterate to provide the output residual norm. Count each Jacobian assembly, factorization attempt, and linear solve actually performed.
In chord mode, for , first evaluate and put . If , return ; this status means only that the residual tolerance was met. If , return . Otherwise, at , refresh by forming , attempting to factor it, and retaining the factorization until the next scheduled refresh. The factorization backend must either report singularity or return a factor object whose solve operation gives the exact unique solution of . If it reports singularity, return . At each correction obtain by calling the solve operation on that retained factor object with right-hand side ; do not refactor or invoke a fresh matrix-only solve. The exact-solve backend contract makes this the mathematical correction in Newton correction for a square vector residual. If the correction has , return ; otherwise set and continue. A refresh period updates the Jacobian every correction; is a chord iteration.
Both modes make no claim that a finite budget reaches an exact root or that a small residual is a forward-error bound. Record the number of Jacobian assemblies, factorization attempts, and linear solves actually performed; a dense LU correction uses one forward and one backward triangular solve. Sparse cost depends on the actual stage matrix and factorization backend and is not bounded here.
Depends on
- A total derivative computes every directional derivative, and its matrix is the Jacobian
- Implicit residuals and their update and derivative units
- Finite-budget Newton for a square vector residual
- Newton correction for a square vector residual
- Continuously differentiable maps, local inverses, and local diffeomorphisms
- The Jacobian matrix of partial derivatives and the gradient in the scalar-valued case
Used by
- Finite budget RATTLE solve with scaled constraint residuals Algorithm
- Implicit stiff time stepping with a branch and residual ledger Algorithm
- Newton can exhaust its budget although the dissipative backward Euler root is unique Example
- One Robertson reaction step: Newton work and the chord reuse tradeoff Example
- The finite budget RATTLE solver returns a status in finite work Theorem
Dependency tree · two levels
17 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
- John C. Butcher, Implicit Runge–Kutta Methods, tutorial accompanying Numerical Methods for Ordinary Differential Equations (standard reference, not scraped)
- Tobin A. Driscoll and Richard J. Braun, Fundamentals of Numerical Computation, §4.5.2 Newton’s method for systems (standard reference, not scraped)