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.
Zero limiting remainder does not make finite residual offspring deterministic
Statement refuted
If , then standard residual resampling has deterministic offspring counts for every finite particle sample, so its residual covariance may always be set to zero.
Facts & Assumptions
Given: The residual-weight notation in Finite-horizon SMC CLT classes and variance recursions and the standard normalized-weight residual algorithm.
Finite-horizon SMC CLT classes and variance recursions: and a normalized Radon–Nikodym weight satisfies .
Multinomial and residual offspring resampling: Residual counts are plus multinomial draws from the fractional remainders of the normalized weights .
Counterexample
Given: Let the proposal law on assign probabilities , and let the importance weights be . Their proposal expectation is one, the target law is , and .
For , the event that the proposal sample contains one , one , and one has probability . On this event the total weight is four and the normalized weights are .
The scaled normalized weights are , so their floor counts are and their fractional remainders are . By [F2] one residual child is drawn, with equal probability from and ; hence the offspring-count vector is random although the limiting proposal remainder integral is zero. This contradicts the Statement.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
6 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.