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.
Stored retarded Euler and distributed midpoint work, storage, and grid alignment
Statement
Fix positive integers , positive , , and . Consider the following finite storage schedule: initialize and retain -vectors for ; at each index , first test an optional nonnegative integer budget , stopping if , and otherwise evaluate one vector , form , and append it. Assume every reached evaluation is defined and returns in finite time. A complete schedule uses exactly calls to and retains state vectors. If , it stops after exactly calls with vectors. Initialization uses history evaluations in either case. Full history storage is real entries. With direct array indexing and a constant-cost scalar floor operation, a query of the piecewise-linear interpolant of the stored vectors costs arithmetic. Counts exclude internal evaluation costs.
For a complete stored history, fix a positive integer and , put , , and . Consider the schedule that initializes and, for , adds to . With returning kernel evaluations, this makes kernel evaluations and history queries, using arithmetic besides kernel evaluations. Streaming the scalar weights uses additional storage; caching all weights uses , excluding the input history. Every stored-grid knot, including a delay breakpoint , encountered by on is a quadrature-cell endpoint. No constant-memory claim is made for the complete stored history.
Facts & Assumptions
Given: The two finite schedules, admissibility conditions, returning evaluations and indexing/cost conventions in the Statement.
Proof
Initialization samples and stores exactly history vectors. After completed updates, induction gives calls to and retained vectors. The next delayed index has already been stored because . Returning evaluations allow the finite loop to reach , or its first budget stop at . Each vector has entries. Since and , , proving the storage bound.
At a query in the stored interval, locates its cell, with the final stored endpoint handled separately. Direct indexing retrieves the two endpoint vectors; linear interpolation takes a fixed number of operations per coordinate. The floor/index work is constant by hypothesis, so the query costs . At a stored endpoint its vector may be returned directly.
Each of the midpoint iterations evaluates one kernel value and one history query, then uses a fixed number of coordinate multiplications and additions. Step 1.2 gives total arithmetic. Streaming the midpoint and scalar weight retains only a constant number of scalars and -vectors, hence extra storage since . Retaining all scalar weights adds ; neither implementation duplicates the input history.
A stored knot appears at exactly when . If this lies in , it is an integer multiple of , hence a quadrature-cell endpoint. Each delay breakpoint is such a knot. Alignment does not require midpoint samples themselves to be stored-grid nodes.
Used by
Dependency tree · 0 levels
Nothing. This result depends on no other item in the library.
Sources
- Nicola Guglielmi and Ernst Hairer, Solving Delay Differential Equations, Chapter 1 (standard reference, not scraped)