Alphabeta Math
AlgorithmAlgorithm: Literature-sourcedProof: Not applicablePipeline-generated
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 adaptive Runge–Kutta controller

Definition

Inputs are an IVP in the sense of First-order systems, initial value problems, and solutions on intervals, y′=f(t,y) on an open domain D⊆R×Rd with initial data (t0,y0)∈D and requested interval [t0,T], where t0≤T and d≥1; an initial proposal 0<hinit≤hmax⁡; an embedded pair with low order p≥1 as in Embedded Runge–Kutta pair and difference estimator; tolerances atol>0 and rtol≥0; safety 0<σ<1; scale bounds 0<γmin⁡≤1≤γmax⁡; step bounds 0<hmin⁡≤hmax⁡; and a positive integer attempt budget N.

Output. Return a record consisting of one of success, failure, minimum-step-rejected, or attempt-budget-exhausted, together with the accepted mesh A=((t0,y0),…,(tm,ym)). The mesh always contains the initial pair and every accepted endpoint; on success, tm=T and ym is the returned endpoint approximation. On any other status, A is the accepted prefix and ym is the last accepted approximation.

Every maximum and minimum below is over a displayed nonempty finite list of real numbers; existence follows from Every nonempty finite set of reals has a maximum and a minimum.

Procedure. Initialize t:=t0, y:=y0, A:=((t0,y0)), and proposal hprop:=hinit. If t0=T, return success with A. For each attempt index k=1,…,N, perform exactly the following steps:

  1. Set h:=min⁡(hprop,hmax⁡,T−t). The last term permits a final clipped step shorter than hmin⁡. If h≤0 before reaching T, return failure with A.
  2. Evaluate the shared stages in tableau order, checking before each evaluation that its time-state input lies in D. If a stage input is outside D, its evaluation is undefined, or its value is nonfinite, return failure with A. Compute both pair outputs; if either output or any arithmetic needed to compute them is undefined, fails, or is nonfinite in the rounded realization, return failure with A.
  3. Define si:=atol+rtolmax⁡(∣(y)i∣,∣(Y)i∣) and Q:=max⁡i∣(Y^−Y)i∣/si, where Y is the high-order value and Y^ the low-order value. If any scale or Q operation fails or is nonfinite in the rounded realization, return failure with A. If Q≤1, first check (t+h,Y)∈D; if not, return failure with A. Otherwise accept: set t:=t+h, y:=Y, and append (t,y) to A. If Q>1, reject and retain t,y,A.
  4. If the attempt was accepted and t=T, return success with A. Otherwise, if it was rejected and h≤hmin⁡, return minimum-step-rejected with A. These terminal checks precede the budget check, so a final accepted step that reaches T succeeds and a rejection at the minimum step reports that safeguard.
  5. If k=N, return attempt-budget-exhausted with A. Otherwise compute g={γmax⁡,Q=0,min⁡(γmax⁡,max⁡(γmin⁡,σ/Qp+1)),Q>0. Set hprop:=min⁡(hmax⁡,max⁡(hmin⁡,gh)) and continue to attempt k+1. A failed or nonfinite rounded computation of g or hprop returns failure with A.

For Q>0, Qp+1 is the unique positive (p+1)st root supplied by Existence and uniqueness of n-th roots: a unique a1/n≥0 with (a1/n)n=a. The exponent 1/(p+1) is a leading-error model for step selection; neither acceptance nor this controller is a global error certificate or a stiffness test.

The mathematical specification evaluates each displayed operation, including maximum, minimum, absolute value, and positive-root evaluation, exactly. A rounded implementation instead applies its fixed finite-format rounding rule to every stage, output, scale, and controller-factor arithmetic operation and uses the resulting stored high and low values in the displayed difference and acceptance test; nonfinite or failed operations return failure. The finite termination theorem applies to either realization when each attempt has finite work. The rounded realization has no a posteriori guarantee: a tolerance below its resolution can be accepted because both stored values coincide.

Depends on

Used by

Dependency tree · two levels

29 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