Roadmap to Reproducibility

A Roadmap to (Computational) Reproducibility

Once data are collected…

Concept	Reason
Do not use a GUI, use a script.	A script can be rerun.
Use an IDE that supports projects, ensuring that references are relative to the root working directory.	The script can be ported to another machine.
Do not overwrite variables, generate a new, derived variable.	Allows you to trace errors.
Use version control.	Track changes over time for workflow transparency.
Maintain Documentation.	Keep a record of tacit knowledge.
Use a language and approach that supports literate programming.1	Make your code intelligible to others.
Manage your code to: a) separate exploratory and confirmatory analyses (use notebooks, like RMarkdown); b) maximize reuse (use scripts for frequently reused code); and c) limit accidentally overwriting objects (functional programming).	Maintain clear delineations between instructions and outputs (functional programming), minimize mistakes / errors (code reuse), separate hypothesis generation from hypothesis testing (notebookes).
Use open file formats and when possible ones that have formal standards.	Maximize persistence in time and portability across software and hardware.
Document your: a) Operating System and version; b) Program and version; c) External packages and version.	Provide a replicable computational framework.
Find a way to account for dependencies - these may be language specific, operating specific, hardware specific.2	Provide a “package” that is a replicable framework.

---

¹
“Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do.”

²
How to Account for Dependencies:

• renv() for language specific
• containers for OS
• emulators for hardware

---

This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License

Built and rendered courtesy of RMarkdown from RStudio