Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/reprohack/reprohack-hq

ReproHack Headquarters
https://github.com/reprohack/reprohack-hq

hackathon reproducible-research reresearch-code-review

Last synced: 26 days ago
JSON representation

ReproHack Headquarters

Lists

README

        

---
title: ReproHack HQ
output: github_document
always_allow_html: yes
---

```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
echo = FALSE, knitr.kable.NA = '', message = FALSE, warning = FALSE
)
library(dplyr)
library(leaflet)
```

Welcome to the ReproHack Headquarters! :tada:

[![Project Status: WIP – Initial development is in progress, but there has not yet been a stable, usable release suitable for the public.](https://www.repostatus.org/badges/latest/wip.svg)](https://www.repostatus.org/#wip) [![Slack](https://img.shields.io/badge/slack-join%20us-brightgreen)](https://reprohack-autoinvite.herokuapp.com/)

[![Newsletter](https://img.shields.io/badge/subscribe-newsletter-blueviolet?style=for-the-badge)](https://tinyletter.com/reprohack-hq)

***


> ## `r emo::ji("construction")` NEW HUB UNDER CONSTRUCTION! `r emo::ji("construction")`
>
> _We are building a custom website to facilitate ReproHack activities going forwards. It is still very much under construction and buggy but hoping to have it functional by early next year._
>
> _You can [check it out](http://annakrystalli.pythonanywhere.com/) or if you have Django skills [contribute](https://github.com/reprohack/reprohack_site)!_

***

## What is a ReproHack
### A one day, hands-on Reproducibility Hackathon

We are all excited by the progress made by many authors to **make their papers reproducible by publishing associated 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 as a learning experience for those who attempt to reproduce the work.

## **Event format**:

During a ReproHack, **participants attempt to reproduce published research of their choice from a list of proposed papers with publicly available associated code and data**.

Participants get to work with other people's material in a low pressure environment and record their experiences on a number of key aspects, including reproducibility, transparency and reusability of materials. At the end of the day we regroup, share our experiences and give feedback to the authors.

It's imperative to note that **ReproHacks are by no means an attempt to criticise or discredit work**. We see reproduction as **beneficial scientific activity in itself**, with useful outcomes for authors and valuable learning experiences for the participants and the research community as a whole.

## **Ways to participate**


### :page_facing_up: **Propose a paper**

##### You've put a lot of effort into making your work reproducible. Now let people learn from and engage with it!

Benefits to authors:

- **Feedback** on the reproducibility of your work.

- **Appreciation** for your efforts in making your work reproducible.

- Opportunity to **engage others with your research**.


### :arrows_counterclockwise: :white_check_mark: **Reproduce**

##### Join us at the ReproHack and get working with other people's material.

Benefits to participants:

- **Practical experience in reproducibility** with real published materials and the opportunity to explore different tools and strategies.

- **Inspiration** from working with other people’s code and data.

- An appreciation that **reproducibility is non trivial** but that opening up your work for more people to engage with is the best way to help improve it.

- An appreciation that **reproducibility has community value beyond just the validation of the results**. For example, access to such materials increases the potential for reuse and understanding of the work.

**Benefits to the whole research community:**

- Assessment of how reproducible papers are ‘out of the box’.

- Evaluation of how successful current practices are and for what purpose.

- Identification of what works and where the most pressing weaknesses in our approaches are.

***

## Contributing

### Run a ReproHack!

Please get in touch if you would like to run a ReproHack. We are working to make materials more reusable and easier to reproduce and also on developing guidance on organising and running an event so that in future folks will be able to run everything independently.
There are currently [reusable materials](https://github.com/reprohack/reprohack-template-shiny) and [instructions for organisers](organiser_instructions.md). However, there are plans to streamline the materials & workflow. At this stage, we also really appreciate contact with organisers in order to both help and to learn from their experiences.

### Hack the ReproHack!

There are a [number of topics](dev_directions.md) we are working on to improve the events and make them reproducible and scalable. Details on the main development directions can be found in the on the

See [Roadmap]() for more details on milestones


***

# Upcoming Reprohacks

```{r}
event_log <- readr::read_csv("data/event-log.csv") %>%
mutate(upcoming = date >= Sys.Date()) %>%
mutate(title = glue::glue("[{title}]({url})"))

event_log %>%
filter(upcoming == TRUE) %>%
select(-lat, - lon, -upcoming, -room, -address, -url) %>%
arrange(date) %>%
knitr::kable()
```

## Past Reprohacks

```{r}
event_log %>%
filter(upcoming == FALSE) %>%
select(-lat, - lon, -upcoming, -room, -address, -url) %>%
arrange(date) %>%
knitr::kable()
```

## Map of Reprohacks

```{r map}
plot_log <- event_log %>%
mutate(color = case_when(upcoming == TRUE ~ "green",
upcoming == FALSE ~ "orange"))

#pal <- colorFactor(c("green", "orange"), c(FALSE, TRUE))

icons <- awesomeIcons(
icon = 'ios-close',
iconColor = 'black',
library = 'ion',
markerColor = plot_log$color
)

plot_log %>%
leaflet() %>%
addProviderTiles("CartoDB.Positron") %>%
addAwesomeMarkers(icon = icons) #%>%
#addLegend("bottomright", pal = pal, values = ~upcoming,
#opacity = 0.7)
```

***

## More on the ReproHack:

- **Blogpost**: [ReproHacking at Opencon London 2017 Doathon](https://rse.shef.ac.uk/blog/opencon-london/)
- **Blogpost**: [Reprohacking at CarpentryConnect Manchester 2019](https://software.ac.uk/blog/2019-08-07-reprohacking-carpentryconnect-manchester-2019)
- **Comunity Call**: Section on ReproHack on [Reproducible Research with R, rOpenSci Community Call](https://vimeo.com/351259131)
- **Blogpost**: [Reproducibility Hackathon Netherlands – the aftermath](https://www.software.ac.uk/blog/2020-01-15-reproducibility-hackathon-netherlands-aftermath)
- **Blogpost**: [N8 CIR ReproHack Northern Tour - Winter 2020](https://n8cir.org.uk/news/reprohacks/)

## Many ways to ReproHack!

![](assets/workflow.png)

***


[![Slack](https://img.shields.io/badge/slack-join%20us-brightgreen)](https://reprohack-autoinvite.herokuapp.com/)

### Subscribe to our Newsletter

[![Newsletter](https://img.shields.io/badge/subscribe-newsletter-blueviolet?style=for-the-badge)](https://tinyletter.com/reprohack-hq)

## Team
- [Florencia D’Andrea](https://github.com/flor14)
- [Daniela Gawehns](https://github.com/DanielaGawehns)
- [Anna Krystalli](https://github.com/annakrystalli)
- [Linda Nab](https://github.com/LindaNab)
- [Ricarda Proppert](https://github.com/RicardaP)
- [Paloma Rojas Saunero](https://github.com/palolili23)