ReproHacks

A sandbox environment

for practicing reproducible research




Dr Anna Krystalli (r-rse) @annakrystalli

TIER2 @ FENS Forum 2024 ReproHack

👋 Hello

me: Dr Anna Krystalli

  • Research Software Engineering Consultant, r-rse

    • twitter @annakrystalli
    • github @annakrystalli
    • email r.rse.eu[at]gmail.com
  • 2018 Software Sustainability Fellow

  • Founder & Core Team member ReproHack


slides: bit.ly/tier2-reprohack-slides

Motivation

Why Open Science



Benefit #1

Transparency as a means of verification


Benefit #2

Transparency as a means of supercharging research cycle

So how are we doing?

Is code and data enough?

If a paper claims to be reproducible but nobody checks it, is it really reproducible?

All skills require practice

Photo by Alexander Grey on Unsplash

Reprohacks

One day reproducibility hackathons



  • How reproducible are papers?

  • How can we provide a sandbox environment to practice reproducibility?

ReproHack History

  • OpenCon Satellite: Berlin, 2016

  • OpenCon Satellite: London, 2017


Inspired by Reproducible Research in Ecology, Evolution, Behaviour, and Environmental Studies course:

  • Reproduce published results from raw data
  • Over a few months and a number of sessions


ReproHack mission: Reproduce paper in a day from code and data

2018 SSI Fellowship

How does it work?

Call for papers

On the day



  • Intro & Set the Tone

  • Select paper and form groups

  • Work with materials and reproduce

  • Regroup & Discuss

  • Feed back to authors

Benefits

ReproHacks are fun

Tips for reviewing

Code of Conduct

Event governed by ReproHack Code of Conduct


Additional Considerations

  • Reproducibility is hard!

  • Submitting authors are incredibly brave!

Thank you Authors! 🙌

  • Without them there would be no ReproHack.

  • Show gratitude and appreciation for their effort and bravery. 🙏

  • Constructive criticism only please!

Selecting Papers

  • Author comments: paper description and why you should choose to reproduce.
  • Tags: Tools, languages & domains
  • No. attempts: No. times reproduction has been attempted
  • Mean Repro Score: Mean reproducibility score (out of 10)
    • lower == harder!

Review as an auditor 📑

Looking for FAIR principles

  • Findable
  • Accessible
  • Interoperable
  • Reusable

Access

  • How easy was it to gain access to the materials?

Installation

  • How easy / automated was installation?
  • Did you have any problems?

Data

  • Were data clearly separated from code and other items?
  • Were large data files deposited in a trustworthy data repository and referred to using a persistent identifier?
  • Were data documented …somehow…

Documentation

Was there adequate documentation describing:

  • how to install necessary software including non-standard dependencies?
  • how to use materials to reproduce the paper?
  • how to cite the materials, ideally in a form that can be copy and pasted?

Analysis

  • Were you able to fully reproduce the paper?
  • How automated was the process of reproducing the paper?
  • How easy was it to link analysis code to:
    • the plots it generates
    • sections in the manuscript in which it is described

Analysis

If the analysis was not fully reproducible 🚫

  • Did results (e.g. model outputs, tables, figures) differ to those published? By how much?
  • Were there missing dependencies?
  • Was the computational environment not adequately described / captured?

Review as a user 🎮


What did you find easy / intuitive?

What did you find confusing / difficult

What did you enjoy?

Feedback as a community member


Acknowledge author effort

Give feedback in good faith

Focus on community benefits and system level solutions

Next Steps!


Submit your own papers!


Host your own event!

reprohack.org



Chat to us:

👋 Thanks for 👀 |