---
title: "Reproducibility in Practice: Data, Code and What Another Lab Can Rerun"
description: "A result that cannot be regenerated from raw data and a script is a claim rather than a method. This stop covers deposition, versioning, and the difference between reanalysing the same data and repeat"
canonical: https://lightmysky.com/learn/science/reproducibility-in-practice-data-code-and-what-another-lab-can-rerun-mt_QuHuEyasFt
source: https://lightmysky.com/learn/science/reproducibility-in-practice-data-code-and-what-another-lab-can-rerun-mt_QuHuEyasFt.md
retrieved: 2026-09-12
---

> **Agent view.** This is the Markdown twin of the page, for tools and assistants.
> When to use this site, and the call that answers each job: https://lightmysky.com/agent-instructions.md
> API description (OpenAPI 3.1): https://lightmysky.com/openapi.json · Authentication: https://lightmysky.com/auth.md
> Pricing: https://lightmysky.com/pricing.md · Catalog: https://lightmysky.com/llms.txt · Full catalog: https://lightmysky.com/llms-full.txt
> Every machine-readable file on this domain: https://lightmysky.com/.well-known/ai-catalog.json
> Ask for Markdown with `Accept: text/markdown`, a `.md` address, or `?mode=agent`.

# Reproducibility in Practice: Data, Code and What Another Lab Can Rerun

A result that cannot be regenerated from raw data and a script is a claim rather than a method. This stop covers deposition, versioning, and the difference between reanalysing the same data and repeating the experiment.

Subject: Science · Area: Scientific Inquiry · Ages 23 to 24
Page: https://lightmysky.com/learn/science/reproducibility-in-practice-data-code-and-what-another-lab-can-rerun-mt_QuHuEyasFt

## Ready when they can

- Package an analysis so a stranger can regenerate a stated figure from the raw data
- Distinguish reproducing an analysis from replicating an experiment, and say what each tests
- Choose an appropriate repository and metadata standard for a stated data type

## Lesson: Hand over work that reruns

A result is reproducible when a stranger regenerates your figure from raw data plus your script, asking you nothing. Deposit both under version control with tool versions pinned and the exact run command written down. Anything less is a claim, not a method.

**Example.** Your plot came from raw.csv plus clean.py at version 1.3 under Python 3.11. The package lists all three plus the one run command. A stranger runs that command and gets your figure back, bit for bit.

Reproducing re-runs your analysis on your data, testing code and claims. Replicating repeats the experiment fresh, testing the phenomenon itself. One checks honesty, the other checks nature: never confuse them.

**Tip.** Deposit by data type: sequences to a sequence archive, tables and code to a general repository, each with standard metadata saying what, who, when, and how. Metadata is what keeps files findable and rerunnable years later.

**Recap.** Pin data, code, and command so a stranger rebuilds every figure alone.

## Practice

8 questions on this page, each with its working shown.

## Needs first

- [Reading a Primary Paper: The Claim, the Figure and the Missing Control](https://lightmysky.com/learn/science/reading-a-primary-paper-the-claim-the-figure-and-the-missing-control-mt_DZE7z5vu9X)
- [Version Control as a Graph of Commits](https://lightmysky.com/learn/computing/version-control-as-a-graph-of-commits-mt_oKsDRKirMy)