Terms Developed in Context
The terms below connect the mathematical model, implementation choices, computed diagnostics, and limits of the scientific claim.
- Validation dossier
A compact record of analytic checks, convergence evidence, uncertainty, provenance, and limitations supporting a result. In this lecture it is used to address Which checks are decisive enough to support the final scientific conclusion?
Model connection: Read the term against Discretization error and the governing relation \(\epsilon_{\rm total}\not\equiv\epsilon_{\rm solver};\quad \epsilon_{\rm total}\sim(\epsilon_{\rm discretization},\epsilon_{\rm sampling},\epsilon_{\rm parameter},\epsilon_{\rm model})\). The relevant computational evidence is a controlled output, residual, invariant, or refinement sequence rather than visual smoothness alone.
Interpretive limit: Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy. This distinction separates numerical behavior from physical accuracy and model adequacy.
- Discretization error
Error caused by representing continuous equations on finite timesteps, grids, or basis sets. In this lecture it is used to address Which checks are decisive enough to support the final scientific conclusion?
Model connection: Read the term against Sampling error and the governing relation \(\epsilon_{\rm total}\not\equiv\epsilon_{\rm solver};\quad \epsilon_{\rm total}\sim(\epsilon_{\rm discretization},\epsilon_{\rm sampling},\epsilon_{\rm parameter},\epsilon_{\rm model})\). The relevant computational evidence is a controlled output, residual, invariant, or refinement sequence rather than visual smoothness alone.
Interpretive limit: Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy. This distinction separates numerical behavior from physical accuracy and model adequacy.
- Sampling error
Random variation caused by estimating a quantity from a finite stochastic sample. In this lecture it is used to address Which checks are decisive enough to support the final scientific conclusion?
Model connection: Read the term against Parameter uncertainty and the governing relation \(\epsilon_{\rm total}\not\equiv\epsilon_{\rm solver};\quad \epsilon_{\rm total}\sim(\epsilon_{\rm discretization},\epsilon_{\rm sampling},\epsilon_{\rm parameter},\epsilon_{\rm model})\). The relevant computational evidence is a controlled output, residual, invariant, or refinement sequence rather than visual smoothness alone.
Interpretive limit: Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy. This distinction separates numerical behavior from physical accuracy and model adequacy.
- Parameter uncertainty
Uncertainty propagated from incompletely known model inputs or fitted parameters. In this lecture it is used to address Which checks are decisive enough to support the final scientific conclusion?
Model connection: Read the term against Model discrepancy and the governing relation \(\epsilon_{\rm total}\not\equiv\epsilon_{\rm solver};\quad \epsilon_{\rm total}\sim(\epsilon_{\rm discretization},\epsilon_{\rm sampling},\epsilon_{\rm parameter},\epsilon_{\rm model})\). The relevant computational evidence is a controlled output, residual, invariant, or refinement sequence rather than visual smoothness alone.
Interpretive limit: Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy. This distinction separates numerical behavior from physical accuracy and model adequacy.
- Model discrepancy
Systematic difference between the adopted mathematical model and the physical system it approximates. In this lecture it is used to address Which checks are decisive enough to support the final scientific conclusion?
Model connection: Read the term against Validation dossier and the governing relation \(\epsilon_{\rm total}\not\equiv\epsilon_{\rm solver};\quad \epsilon_{\rm total}\sim(\epsilon_{\rm discretization},\epsilon_{\rm sampling},\epsilon_{\rm parameter},\epsilon_{\rm model})\). The relevant computational evidence is a controlled output, residual, invariant, or refinement sequence rather than visual smoothness alone.
Interpretive limit: Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy. This distinction separates numerical behavior from physical accuracy and model adequacy.
Problem and physical meaning
A research computation needs a model argument, numerical evidence, and a bounded interpretation. The strongest claim is often the one that survives changes in resolution, timestep, seed, and plausible physical assumptions.
Which checks are decisive enough to support the final scientific conclusion? Begin from the scientific observable or state variable, and name what is directly specified versus inferred. The model should be simple enough to validate, but not quietly presented as the entire astrophysical system.
Model and derivation
The governing expression for this lecture is:
Define the symbols and the independent variable before numerical evaluation. Dimensional analysis checks that both sides have matching units; if the model is dimensionless, state the adopted scale factors and the transformation back to physical units.
A research computation needs a model argument, numerical evidence, and a bounded interpretation. The strongest claim is often the one that survives changes in resolution, timestep, seed, and plausible physical assumptions.
Numerical implementation
State the scientific question; identify inputs and provenance; choose a domain solver; design a convergence and uncertainty plan before running; compare an independent method or analytic limit; archive code, environment, data, and validation report.
Keep physical quantities and numerical arrays conceptually separate. Convert units at well-defined boundaries, preserve raw inputs, and record dtype, solver, tolerances/timestep, grid, and software versions. A numerical method is part of the model evidence, not an invisible implementation detail.
Worked, programmatically computed example
The final validation dossier retains four distinct measures: three-body energy drift 5.33e-13, shock L1 error 0.00521, transmission standard error 0.00244, and fitted residual RMS 3.0897 m/s.
These values are generated in src/astr474_computations.py, then shared with lecture/lab/assignment renderers. Re-run the generator after changing an input; do not hand-edit a displayed result without recomputing dependent artifacts.
At least one independent check is required: an analytic solution, a second numerical method, a conservation law, or a controlled convergence sequence. When these disagree, diagnose units, frame, discretization, source terms, and model scope before selecting a result.
Error budget and limitations
Do not collapse distinct errors into one unlabeled percentage. Solver convergence does not reduce parameter uncertainty or model inadequacy.
Classify each uncertainty before combining terms: local/global solver error, timestep or spatial discretization, Monte Carlo sampling, parameter uncertainty, measurement uncertainty, and model discrepancy are not interchangeable. Conservation can test internal consistency but does not prove the model is physically complete.
Connection to evidence and research practice
Lab 07 and PS07 deliver a compact, independently audited computational research record.
For real parameters, the source record distinguishes the fetched product and epoch from derived values. For synthetic experiments, the initial conditions, generator, seed, and exact file are recorded. A simulation is not an observation, even when its parameters resemble a real object.
Misconceptions to avoid
- More displayed digits do not imply more physical accuracy.
- A successful solver exit or smooth plot does not establish convergence.
- Agreement between two solvers with the same wrong model is not independent physical validation.
- A formal covariance or Monte Carlo interval is conditional on the adopted model and noise process.
Study and review questions
- Which checks are decisive enough to support the final scientific conclusion?
- Which numerical parameter would you vary first, what observable would you track, and how would you know the sequence reached an asymptotic regime?
- Design one independent check and state what failure would change your scientific interpretation.
Preparation for the next lecture: explain how this method's assumptions change when the problem becomes more coupled, stochastic, or data-driven.
Lecture-specific derivation and assumptions
A defensible result has at least four distinct error channels: numerical/discretization error, stochastic sampling error, uncertainty in fitted or physical parameters, and model discrepancy. They cannot be combined until their meanings, dependence, and probability interpretation are specified. A convergence study addresses one numerical channel; a posterior or covariance addresses parameter uncertainty conditional on a model; neither absorbs missing physics. A claim should therefore identify the observable, data level, algorithm, validation, and exact limitation.
Algorithm trace and computed-output interpretation
Choose one course result and create a claim-evidence table. For the 1-AU orbit, for example, compare the analytic period with a timestep sweep, report invariant/endpoint diagnostics, and identify the model-to-ephemeris residual as a combination of frame and omitted-force discrepancy. For the shock result, use mass conservation and resolution error but state that the 512-cell profile is not exact. Build the abstract only after the evidence table fixes what is and is not supported.
Computed result: The final validation dossier retains four distinct measures: three-body energy drift 5.33e-13, shock L1 error 0.00521, transmission standard error 0.00244, and fitted residual RMS 3.0897 m/s.
The strongest conclusion may be narrower than the most interesting scientific story. Preserve separate columns for numerical error, stochastic error, parameter uncertainty, and model discrepancy; mark inapplicable categories with a reason instead of a fabricated number. Peer review should be able to rerun the code and challenge the assumptions independently.
Two-meeting teaching arc
Each weekly module is taught in two 75-minute meetings. The sequence below includes a formative check in each meeting and is intended to use the lecture's worked computation, not merely present it.
- Meeting 1 (75 min): 10 min synthesis question; 20 min error taxonomy; 20 min evidence-to-claim mapping; 20 min compare orbital and shock examples; 5 min identify overclaim risk.
- Meeting 2 (75 min): 10 min recap; 20 min construct a claim-evidence table; 25 min peer audit and alternative explanation; 15 min draft bounded abstract; 5 min final validation commitment.
Targeted study questions
- Which error term is reduced by grid refinement, and which is not?
- How would you test whether an omitted physical process dominates solver error?
- Rewrite a conclusion so its precision does not exceed the least-constrained evidence channel.
References and provenance: course reference log. Generated 2026-09-25.