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.
An approximate D-optimum need not be an exact three-run design
Example
Take candidates , regression vector , and . The approximate design with weights and has and is D-optimal. For exactly three runs, the largest possible determinant is , so no exact three-run allocation attains the approximate optimum.
Facts & Assumptions
Given: The three candidate points, regression vectors, and approximate design in the Example.
Approximate designs and linear-model optimality criteria: an exact -run design has weights with nonnegative integer counts summing to .
Equivalence criterion for D-optimal approximate designs: a nonsingular approximate design is D-optimal when every candidate leverage is at most , with equality on its support.
Verification
The information matrix is , with determinant and inverse . Hence the leverage at is , giving , , and . By [F3], all candidates satisfy and equality holds on the support , so is D-optimal.
For an exact three-run design let be the nonnegative integer counts with sum . Substitution into [F1] and the exact-count convention [F2] gives .
The ten count triples give determinants as follows: give ; give ; give ; and gives . Thus the exact maximum is , attained by either endpoint allocation with counts and .
Since , the exact three-run optimum and the approximate optimum differ. This finite calculation concerns only the stated candidate set and run count.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
11 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
- Stephen Boyd and Lieven Vandenberghe, Convex Optimization, §7.5 (standard reference, not scraped)