ReproNim Reproducible Basics Module

Other day-to-day reproducible practices


Teaching: 25 min
Exercises: TODO min
  • How is reproducibility critical to fixing software bugs?

  • What steps can you take toward sharing your studies reproducibly?

  • Underestand best practices for submitting bug reports

In this final lesson, we’ll cover some miscellaneous best practices for reproducibility in basic day-to-day activities. Although individually some practices may seem insignificant, they add up.

A good bug report is a reproducible one

“Reproducibility” is at the heart of what constitutes a good bug report.


Additional materials:

Overall summary:

Have reproducibility and openness in mind from the beginning

The devil is in the details” and “Talk is cheap, show me the code” (L. Torvalds, Linux project) are two common idioms pointing to the fact that a verbal description alone, as typically condensed into a paper’s Methods section, is rarely sufficient to reproduce an empirical result.

This is why it’s so important to share relevant data, code, computation environments, etc. However, if you delay preparing your materials for sharing, you might find it difficult, if not impossible, to share your work later on – as your project has progressed forward or may even be completed. Keeping the goal of sharing in mind right from the start will make sharing easier when you’re actually ready or asked to share.


Additional materials:

Key Points