Alphabeta Math
AlgorithmAlgorithm: AI-adaptedProof: 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 multiplicative update for approximate D-optimal design

Definition

Let p≥1, let X be a finite nonempty candidate set, and let fx∈Rp be the feature vector for each x∈X. An approximate design ξ and information matrix M(ξ)=∑xξxfxfxT use the convention of Approximate designs and linear-model optimality criteria. The same vectors may be scalar-observation sensitivities at a fixed parameter, as in Finite nonlinear observation designs, local identifiability, and weighted information, with a scalar precision absorbed into fx. The procedure uses exact arithmetic.

Input: A finite nonempty X, p≥1, its feature vectors (fx)x∈X, an approximate initial design ξ(0), and a finite nonnegative integer budget N counting weight updates.

Procedure: Form M0=M(ξ(0)). If M0 is not positive definite, return (ξ(0),undefined violation,invalid initial design). Otherwise, for k=0,1,…,N, with current ξ(k) and Mk=M(ξ(k)), compute sx(k)=fxTMk−1fx(x∈X),vk=max⁡x∈Xsx(k)−p. If vk=0, return (ξ(k),vk,equivalence-certified). If k=N, return (ξ(k),vk,budget-exhausted). Otherwise set ξx(k+1)=ξx(k)sx(k)p(x∈X), form Mk+1=∑xξx(k+1)fxfxT, and continue.

Remarks

Finite-budget multiplicative design updates preserve the simplex and nonsingularity ↗ proves preservation of positive definiteness and the bounds of at most N updates and N+1 sensitivity scans. A nonzero returned violation is reported as-is; it is not an exact D-optimality certificate. The exact integer allocation problem remains separate from this approximate-weight procedure.

Depends on

Used by

Dependency tree · two levels

16 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