Reproduce and validate a result
Reproduction becomes useful when the result is small enough to specify exactly and the scientific claim is narrow enough to fail. This lesson uses one normalized heavy-scalar exchange channel to separate three questions: does the original procedure run, can the stated result be obtained again, and does a check with different failure modes support the physical interpretation?
Required background. Bring the bounded claim and source trace from Literature, sources, and claim tracing together with the assumptions, convention translation, evidence basis, and cutoff from the scope and conventions sheet. The heavy-field calculation comes from effective field theory and matching. If tolerances, precision, or provenance are unfamiliar, first use the numerical and reproducibility review.
Separate execution, reproduction, and validation
Section titled “Separate execution, reproduction, and validation”Terminology varies across communities, so state the operation rather than relying on a label. This page uses the following distinctions, consistent with the operational discussion in National Academies 2019, ch. 3:
| Operation | What is held fixed or changed | Question answered | What it does not establish |
|---|---|---|---|
| Rerun an implementation | Same source, procedure, and inputs in the intended environment | Can this implementation execute again and recover its output? | Independence from its formulas, design, or defects |
| Reproduce a specified result | A new calculation follows the same mathematical specification, preferably with separately written analysis | Can the declared numbers be obtained without relying on the original execution path? | That the specification represents the intended physics |
| Validate the scientific claim | A limiting case, identity, scaling law, alternative formulation, or other check can fail for a different reason | Does evidence beyond output agreement support the interpretation in its stated domain? | A stronger claim outside the tested observable, assumptions, or regime |
A clean-environment rerun is valuable evidence about instructions and dependencies. It is not, by itself, independent scientific evidence. Two implementations can agree because they share the same incorrect equation; two environments can disagree while the analytic claim remains sound.
Fix a bounded heavy-exchange claim
Section titled “Fix a bounded heavy-exchange claim”Use the same two-scalar model as in the preceding claim trace: a light real field , a heavy real field of mass , and interaction . Eliminating at tree level gives
In one exchange channel, isolate the momentum-dependent factor
Normalize away the low-energy coefficient and define
In four spacetime dimensions in mass units, so both and are dimensionless; is a unit-independent expansion parameter.
The result to reproduce is deliberately limited:
For the real inputs , compute , its leading approximation , and its next approximation . Verify the exact relative errors and their scaling.
This normalized channel is the momentum-space image of the local expansion
because on the exchanged momentum. It checks the sign, expansion parameter, and first two local terms in this channel. Manohar develops this integration and propagator expansion in Manohar 2018, §§3.5, 4.1–4.2, and 5.4, preprint pp. 17–20 and 37, PDF.
It does not prove the full decoupling theorem. It omits other exchange channels, field and vertex renormalization, loop matching, scheme dependence, operator mixing, and known situations in which naive decoupling assumptions fail. The general low-momentum theorem has additional hypotheses and a much broader argument Appelquist and Carazzone 1975, pp. 2856–2861.
Derive the exact residuals before computing
Section titled “Derive the exact residuals before computing”Define signed residuals by approximation minus exact result:
Therefore the relative errors are
The expected values are:
| Exact | |||
|---|---|---|---|
For these positive inputs, both approximations lie below the exact result and NLO is closer than LO. That sign check is capable of exposing a swapped denominator or a wrong derivative-operator sign.
Specify inputs, outputs, and tolerance exactly
Section titled “Specify inputs, outputs, and tolerance exactly”Use this calculation specification before either route below.
Inputs. The ordered binary64 values are
[0.05, 0.10, 0.20]. They represent the dimensionless ratio in a
single real channel. The prescribed run contains no random input. The broader
series condition is ; a program must not report the series as convergent
at or beyond that boundary.
Outputs. For each input, return the columns
x, exact, lo, nlo, residual_lo, residual_nlo, relative_lo, and
relative_nlo in input order. Compute with unrounded values; rounding belongs
only to presentation.
Tolerance. Require the echoed x value to have the input bit pattern.
Compare exact, lo, nlo, both residuals, and both relative errors with
the analytic values using an absolute tolerance of . Also
require the algebraic identity for each row.
These are deterministic binary64 tolerances for this well-conditioned range,
not general EFT uncertainties.
Provenance. Record the mathematical specification, source revision or content hash, script hash, exact command, operating system and architecture, runtime and patch version, numeric type, input bytes and checksum, standard output and checksum, warnings, and every modification made after the first clean attempt. There are no dependencies beyond the language runtime in the short route below; if a notebook, dataframe library, or plotting package is added, record its exact version and execution order.
Use an analytic route or a short code route
Section titled “Use an analytic route or a short code route”Analytic route
Section titled “Analytic route”Treat the inputs as the exact rationals , , and . Evaluate , , and as rational numbers, then compute the signed and relative residuals before converting to decimals. This route has no floating- point tolerance; the equalities are exact. It is the reference against which the binary64 calculation is compared.
Short code route
Section titled “Short code route”The following standard-library-only Python is sufficient:
xs = (0.05, 0.10, 0.20)
for x in xs: exact = 1.0 / (1.0 - x) lo = 1.0 nlo = 1.0 + x residual_lo = lo - exact residual_nlo = nlo - exact relative_lo = abs(residual_lo / exact) relative_nlo = abs(residual_nlo / exact) print(x, exact, lo, nlo, residual_lo, residual_nlo, relative_lo, relative_nlo)Run it from an otherwise empty working directory with the recorded runtime. Redirect or copy the unrounded output only after the command and script hash have been captured. A spreadsheet or another language is equally suitable if it implements the same specification and records its calculation order.
Rerun, reproduce, then validate
Section titled “Rerun, reproduce, then validate”Perform the three operations separately and preserve each outcome.
- Rerun. Execute the recorded script with the recorded binary64 runtime, inputs, command, and clean working directory. Compare every output column with the predeclared values and tolerances. This tests the execution instructions and environment.
- Reproduce. Recalculate the table by the exact rational route or by a separately written spreadsheet or program. Do not copy the original residual calculation. This tests whether the specified result survives a different execution path.
- Validate. Derive the geometric-series remainder, test its predicted scaling, and connect the momentum expansion to the local operator. These checks can reject an implementation that reproduces a few rounded numbers for the wrong reason.
Report the evidence in bounded language:
| Outcome | Conclusion supported |
|---|---|
| Clean rerun agrees | The recorded implementation and environment recover the declared output |
| Independent reproduction agrees | A separate calculation implements the same numerical specification |
| Remainder, scaling, and local-operator checks agree | The bounded one-channel expansion is supported in the tested range |
| All three agree | The one-channel result has reproducible output and independent checks; the omitted channels, loops, and theorem hypotheses remain untested |
If the rerun fails but both analytic routes agree, report an environment or execution problem rather than a refutation of the series. If the outputs agree but the independent identity fails, report that the numbers were recovered without validating the stated calculation.
Use a check with different failure modes
Section titled “Use a check with different failure modes”For any nonnegative integer and , the finite geometric series obeys
The relative remainder after order is therefore . Reducing by a factor of two predicts
LO must improve by a factor of and NLO by a factor of . The pairs in the table test both predictions without using the decimal value of as the reference. Also verify and the negative signed residuals for positive .
The operator check fails differently again. Solving the heavy-field equation and expanding tests the sign and normalization of the local terms before evaluating any chosen . It still shares the same tree-level model and one-channel reduction, which is why the stronger decoupling claim remains outside the evidence.
Triage a failure before changing anything
Section titled “Triage a failure before changing anything”Preserve the first failed output, then locate the earliest layer that can explain it.
| Symptom | First checks | Appropriate response |
|---|---|---|
| Recorded command does not start | Script hash, path, runtime, permissions, and working directory | Repair the execution description without changing the scientific input |
| Same script produces different rows | Input bytes, numeric type, locale, hidden state, and source revision | Isolate the execution difference and retain both outputs |
| Rerun agrees but independent route differs | Mathematical specification, sign convention, copied formula, and rounding order | Resolve the specification before interpreting physics |
| Table agrees but fails internally | Output may be hard-coded, rounded too early, or computed from inconsistent columns | Reject the calculation and expose the dependency between columns |
| Identity passes but error scaling fails | Approximation order, residual definition, input ratio, or domain is wrong | Narrow the numerical claim and repair the convergence test |
| Every check passes only near | The asymptotic claim may be sound but the requested range may be too wide | State the tested range; do not enlarge it without new evidence |
| A result is quoted for | The geometric expansion is outside its convergence disk | Reject the EFT-series interpretation even if the rational function is finite |
Do not widen a tolerance merely to accept the desired result. If a source or environment modification is required, retain the original failed attempt, state the change, and repeat every affected check.
Copyable reproduction bundle
Section titled “Copyable reproduction bundle”This compact bundle is sufficient for the present deterministic calculation and can be extended for data or stochastic work.
source claim and exact locator:bounded scientific claim:explicit nonclaim:scope, assumptions, and convention translation:
mathematical specification:ordered inputs, units, and input checksum:required output columns and order:predeclared tolerances and justification:
source revision and script checksum:runtime, operating system, architecture, and numeric type:exact command and working-directory assumptions:standard output, warnings, and output checksum:changes after the first clean attempt:
independent reproduction route:identity, remainder, and scaling checks:shared assumptions between the two routes:
failure classification and retained evidence:strongest conclusion supported:next unanswered question:For a stochastic calculation, add the random generator, stream construction, seed policy, raw samples, autocorrelation treatment, estimator, and covariance. For external data, add acquisition date, release identity, checksum, units, selection, calibration, and license.
Check your understanding
Section titled “Check your understanding”1. Recover both exact relative errors
Section titled “1. Recover both exact relative errors”Starting from , derive the signed LO and NLO residuals using the definition approximation minus exact result. Then divide by .
Solution
At LO,
At NLO,
Because ,
For positive , both signed residuals are negative: the two truncated sums underestimate the exact rational function.
2. Measure the observed order without using the exact decimals
Section titled “2. Measure the observed order without using the exact decimals”Use the relative errors at and to compute
for LO and NLO.
Solution
At LO, the errors are and , so
At NLO, the errors are and , so
The refinement test recovers the predicted first- and second-order relative remainders. It tests scaling, not the broader heavy-field theorem.
3. Classify three successful calculations
Section titled “3. Classify three successful calculations”Classify each result and state its evidence boundary:
- the recorded script runs in a new empty environment and reproduces its old output;
- a second person evaluates the exact rationals in a spreadsheet built from the mathematical specification; and
- a derivation proves the finite-series remainder and its factor-of-two scaling.
Solution
The first is a rerun. It supports the sufficiency of the environment and execution instructions, but it shares the implementation and its defects.
The second is an independent reproduction of the specified result to the extent that the spreadsheet was written independently. It can expose defects in the original script, but both routes still share the mathematical specification.
The third is a validation check for the bounded series claim. It can expose a wrong approximation order or remainder even if selected table values were copied correctly. It does not test other exchange channels, loops, or the hypotheses of a general decoupling theorem.
4. Detect a wrong denominator sign
Section titled “4. Detect a wrong denominator sign”Suppose an implementation computes . At , compare it with the expected value and test . Which checks fail?
Solution
The wrong result is
whereas the expected value is
Their difference is about , far above the declared tolerance. The independent identity also gives
The numeric comparison, algebraic identity, sign of the residual, and expected low- series all fail. Enlarging the tolerance would conceal a model error, not accommodate ordinary roundoff.
Continue to uncertainty and disagreement
Section titled “Continue to uncertainty and disagreement”Keep the source trace, scope sheet, first clean run, independent reproduction, and every failed check together. They distinguish an environment disagreement from a numerical mismatch or a challenge to the scientific claim.
Next, use Uncertainty, disagreement, and negative results to compare results whose inputs, approximations, or evidence do not align. For a larger computational target, the computational field theory pathway supplies convergence, correlated uncertainty, and provenance requirements.
References
Section titled “References”- Thomas Appelquist and J. Carazzone, “Infrared Singularities and Massive Fields,” Physical Review D 11 (1975), 2856–2861, doi:10.1103/PhysRevD.11.2856.
- Aneesh V. Manohar, “Introduction to Effective Field Theories,” in Effective Field Theory in Particle Physics and Cosmology: Lecture Notes of the Les Houches Summer School, Volume 108, edited by Sacha Davidson, Paolo Gambino, Mikko Laine, Matthias Neubert, and Christophe Salomon (Oxford: Oxford University Press, 2020), 47–136, doi:10.1093/oso/9780198855743.003.0002; author manuscript, arXiv:1804.05863v1 (2018).
- National Academies of Sciences, Engineering, and Medicine, Reproducibility and Replicability in Science, Washington, DC: National Academies Press, 2019, doi:10.17226/25303.