No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github
.gitignore
HOLD.html
LICENSE
README.md

README.md

Welcome to the #OpenConBerlin 2016 #ReproHack!


24 Nov 2016 1pm - 6pm (or till we get kicked out)

Technical University of Berlin, Centre for Entrepreneurship
Hardenbergstraße 38, 10623 Berlin

***

We're kicking off OpenCon Berlin 2016 with a

hack / creative collaborative coding event!

There'll be plenty of options to work on a variety of projects according to skills and interest including:


but we have also come up with a core theme:

a paper reproducibility hack!

We are all excited by the progress made by many to make their papers fully reproducible by publishing code and data. We know how challenging it can be so we want to showcase the value of the practice, both for original authors and and as a learning experience for the reproducers.

Inspired by Owen Petchey's Reproducible Research in Ecology, Evolution, Behaviour, and Environmental Studies course, where students attempt to reproduce the analyses and figures of a paper from the raw data, we want to attempt to do the same. While they take a few months over a number of sessions, we only have a day so instead we'll be trying to do the same but with papers that have also published code.

What we love about this approach, and why we think it fits well in the space of a hack, is that it provides a low-pressure environment to actually get working with other people's code and data. Attempting reproduction provides an opportunity to test how reproducible papers are 'out of the box', enabling evaluation of how successful current practices are, identifying what worked and where the most pressing weaknessess are.

This is by no means an attempt to discredit work so consent by authors will be sought and their involvement is encouraged. We see reproduction as beneficial scientific activitiy in itself, with useful outcomes for the papers and valuable learning experiences for the participants. We hope to feedback our experiences to authors and of course spread the word on successful practice!

a collaborative output:

We want to collaborativelly collate and communicate our experiences and outputs during the session. By collating information and discussions openly through github, collaboratively contributing narrative through etherpads, we hope to end up with at least a comprehensive blog post or potentially a short paper using overleaf.



Two ways to get involved:

Nominate a paper

We invite nominations from anyone, especially if you would like to test one of your own papers! Either way, we encourage proponents to seek consent from the original authors for their nominations.

Current list of proposed papers


Register as a participant

Join us at the hack to dig into exciting science, learn more about reproducibility, working with other people's code and data and more!


On the day

This is the master repo of the hack. We'll collect information on the teams and projects through issues in this repo.

Authors

We encourage authors that are keen, to be available for participants to reach out to for guidance or even just to say hello! We've set up a gitter channel as a public lobby where you can also reach the organisers prior to the hack. You can start discussions through issues in each project repo and we've also set up a public, collaborative hackpad.

Participants

1. Project and team selection

We'll start by discussing the papers proposed and form into teams. We want to use github to keep track of the materials produced during the hack so we encourage teams to ensure they have someone with github skills on board.

2. Create project github repo

Individuals teams are requested to create their own github repo from which to coordinate individual projects.

3. Register your project

4. Work on your project!

Collect any materials generated during the hack in your teams's github repo. If you're trying to reproduce a paper, we recommend you do this in a notebook or .Rmd literate programming document. Here's an examples of such an output, the raw Rmd code (link to .Rdm file) used to create it and the github directory containing materials associated with the reproduction.

5. Record your experience

We encourage teams to track their experiences. Here's a few suggestions


6. Contribute team feedback to the blogpad

The most useful output is the experiences we collect on the blogpad which will form the basis for the final blogpost.

  • We ask teams to at least contribute a section around their project (copy and complete template).
  • There's also a section in the INTRO where both authors and participants can provide some feedback on their motivations and experiences individually.

N.B. Please sign in to each etherpad, within the pad and in the upper right corner to link your name to a colour.