Notebook Reproducibility Issues

Notebook reproducibility issues record failures in computational artifacts: broken execution, stale dependencies, missing data, changed package behavior, benchmark failures, or figure outputs that no longer match their source notebooks.

No public notebook reproducibility issue entries have been recorded yet for the current draft build.

What Belongs Here

Record an issue when:

• a notebook fails from a clean environment,
• package behavior changes a result,
• a benchmark no longer passes,
• a generated figure cannot be reproduced,
• a random seed or dataset is missing,
• a notebook output disagrees with the page using it,
• an environment file is missing or stale.

Entry Format

Field	Meaning
ID	stable issue identifier
notebook or artifact	path
affected page	page using the output
issue type	execution, dependency, benchmark, data, figure, or environment
status	reported, confirmed, fixed, broken, archived, or superseded
environment	recorded or missing environment
benchmark	failed or missing check
correction	change made
date fixed	date

Status Mapping

Use the status labels from Reproducibility Status:

• reproduced,
• reproduced_with_warnings,
• needs_update,
• broken,
• archived,
• conceptual_only.

If a notebook is marked broken, pages should not cite it as evidence until fixed.

Triage Checklist

1. Run from a clean environment.
2. Confirm package versions.
3. Check benchmark cells.
4. Compare generated outputs against committed figures or tables.
5. Decide whether the issue is numerical, environmental, or editorial.
6. Update status and affected pages.
7. Run the local build.

Cross-Links

• Software, Notebooks, and Benchmarks
• Notebook Index
• Environments
• Reproducibility Status
• Benchmark Problems

References

• Project Jupyter, Jupyter Documentation.
• The Turing Way Community, The Turing Way.
• Versioning and Review Policy