I recently gave a presentation on reproducibility to my organization: “Reproducibility from a Mostly Selfish Point of View.” You can find the slides here on figshare.
I am grateful to the following for source material and inspiration:
- Florian Markowetz’s great article “Five selfish reasons to work reproducibly”
- Karl Broman’s reproducible research course introduction
- A series of great suggestions on the literature from Gabe Becker
- ROpenSci’s reproducibility guide
- Titus Brown’s latest post on the SWC listserv
I broke the talk into two sections: “Why” and “How”. Why was, as the title suggests, primarily focused on the benefits of reproducibility to us, and I proceeded from avoiding negatives (risk avoidance) to creating positives (more impact). In How I tried to be very high-level, talking about major concepts in reproducibility, and then talking generally about the tools that I have used for each, emphasizing that they may not be the right tools for everyone. Then we had a discussion about the most promising areas and tools to start with.
This went remarkably well. A few quick thoughts:
-
Many people are primed for this topic. The steady drum of reproducibility-related stories in the science press over the past few years has heightened awareness of this stuff.
-
Despite my avoiding a focus on openness, open-data and code mandates came up a lot, because people want to reduce the effort involved in getting code and data in shape to share per these requirements.
-
The biggest response in terms of positives came from talking about impact, rather than risk management or productivity (though those resonated as well). As I put it, “If we’re going to share, let’s share impressively.” There was a lot of talk about new things we could do, and new audiences we could reach, with additional research products that emerge from reproducible workflows. An example I like is Andrew Rambaut’s MERS data. Rambaut did the work of aggregating this for his own analyses, but by releasing (and updating) the data set with a nice little D3 data viewer on top of it he provided the community with a great tool and increased the visibility of his own work.