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.
Multi-coil MRI benchmark
Example
In the InverseBench multi-coil knee MRI case, a complex image with produces one k-space data vector per receiver coil:
Here is the number of coils, is multiplication by the sensitivity map of coil , estimated for each slice using ESPIRiT as implemented in SigPy, is the discrete Fourier transform, k-space is the Fourier-coefficient data space, selects the acquired k-space entries, and is the raw measurement noise in that coil. With these operators fixed, the measurement map is linear in ; the paper does not assume Gaussian noise for the raw-data benchmark. Its fastMRI knee split contains training images, hyperparameter-search images, and test images, preprocessed to . For the reported metrics in Tables 4 and 5, the reference ground-truth image is the magnitude image of the minimum-variance unbiased estimator (MVUE); these magnitude-MVUE images are also used as training ground truths for Residual UNet and E2E-VarNet. The reported test metrics include peak signal-to-noise ratio (PSNR), structural similarity index measure (SSIM), and data misfit.
Example references
Facts & Assumptions
Given: The finite complex image space, per-slice ESPIRiT-estimated coil sensitivity maps, the fixed Fourier/subsampling operators, raw coil measurement vectors, the magnitude-MVUE ground-truth convention for the reported metrics, and the train/search/test split stated in the Example.
Benchmark risk, compute budgets, and uncertainty records: a benchmark fixes its observation model, noise description, loss/metric, evaluation law, and tuning protocol.
Scope of InverseBench findings: the empirical MRI results are for the specified multi-coil knee data and test split, not a theorem for other image populations.
For an explicit conditional finite-data benchmark, supply the actual nonempty training, validation, and test lists of the stated sizes, including realized observations, target images, operator metadata, and valid discrete forward values. Let be the finite set of labelled cases, with its full power-set sigma-algebra; labels distinguish repeated images. Let with Euclidean distance and Borel sets, and let be the observation-and-operator-metadata space, a finite disjoint union of finite-dimensional Borel spaces if coil counts or data shapes vary; include each case's coil sensitivities and mask in its observation metadata. For case , set (its magnitude-MVUE reference image), (its discrete noiseless forward data), and (its recorded data, with the same metadata). For the coil data, the conditional residual law is the point mass at the recorded residual ; it is not asserted Gaussian, independent of the state, or a law for unobserved acquisitions. Thus describes replay conditional on these realized lists, not a physical law for repeated MRI acquisitions. Set , where is the test index set and ; use the analogous uniform empirical validation law. Take to be the point mass at the entire supplied fitting record, including training/tuning lists and seeds. This conditional specialization supplies laws, not just sample counts, and is not a reconstruction of the paper's full evaluation protocol.
Supply each candidate's complete fitting/tuning procedure and deployed measurable rule , with all seeds fixed. Fix the loss and a radius before testing. The uncertainty diagnostic is empirical coverage , targeting coverage of the balls of radius centered at under . Evaluate every test case once and average its loss. Before fitting or evaluation, supply finite upper bounds for every applicable forward, adjoint, gradient, ODE-evaluation, iteration/sampling, and runtime count, marking inapplicable entries as not applicable, together with hardware, precision, software/model versions, seeds, tuning data, and stopping tolerances. A procedure must return within these bounds or record failure; its deployed rule returns the zero image on failure. Retain that case in both aggregates and report every status and realized count. These supplied procedures and budget records are parameters of this mathematical specialization; the coverage statistic is not a reported InverseBench calibration result.
Verification
With , , and each fixed, is a linear map on ; therefore the displayed observation equation is a linear multi-coil measurement model for each .
For each labelled case in [A1], is a probability measure. Every function on the finite truth space is measurable, including for each Borel observation set . Thus this is an explicitly specified probability kernel, and , , and the empirical test/validation and point-mass fitting laws are measurable or probability-valued as required by [F1]. This conditional construction uses recorded raw data and makes no inference of a physical noise law from the term "raw noise."
The squared loss and ball-membership event in [A2] are product-measurable for the magnitude-image targets and measurable deployed rule. Their empirical-law integrals equal the declared averages, including fallback outputs. The procedures, budgets, metadata, and retained statuses in [A2] complete this finite-data instance of [F1]. The paper's PSNR/SSIM/data-misfit reports retain their original meaning and scope in [F2]; the chosen squared-error and coverage protocol is an explicit specialization, not a claim that the paper specified this diagnostic or a physical observation kernel.
Depends on
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
7 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.