title: "Reproducible Research"

- Mathematics (400 BC?)

- Write scientific paper, Galileo, Pasteur, etc. (1660s?)

- Publish a pidgin algorithm and describe simulation datasets (1950s?)

- Sell magtape of code and data (1970s?)

- Place idiosyncratic dataset & software at website (1990s?)

- Publish datasets and scripts at website, eg. biology, political science, genetics, statistics (2000s?)

- Hosted integrated code and data (2020s?)

<small>Gavish & Gonoho AAAS 2011, Oxberry 2013</small>

<br><small> Claerbout and Karrenbach, Proceedings of the 62nd Annual International Meeting of the Society of Exploration Geophysics. 1992</small>

- **Verification & Reliability**: Find and fix bugs. Today's results == tomorrow's.

- **Transparency**: increased citation count, broader impact, improved institutional memory

- **Efficiency**: Reduces duplication of effort. Payoff in the (not so) long run

- **Flexibility**: When you don’t 'point-and-click' you gain many new analytic options.

**Technical**

- Classified/sensitive/big data

- Nondisclosure agreements & intellectual property

- Competition

- Neither necessary nor sufficient for correctness (but useful in disputes)

**Cultural & personal**

- Few follow even minimal reproducibility standards.

- Few expect reproducibility

- No uniform standards

- Inertia & embarassment

<img src="img_12/peng-spectrum.jpg" alt="alt text" width="800">

<small>Peng 2011, Science 334(6060) pp. 1226-1227</small>

<img src="img_12/peng-pipeline.jpg" alt="alt text" width="600">

<small><small>http://www.stodden.net/AMP2011/slides/pengslides.pdf</small></small>

1. Enter data in Excel

2. Use Excel for data cleaning & descriptive statistics

2. Use ArcGIS and use point-and-click options for processing and visualization

3. Import data into SPSS/SAS/Stata for further analysis

4. Use point-and-click options to run statistical analyses

5. Copy & paste output to Word document, repeatedly

<small></small>

- Version control is ad hoc

- Excel handles missing data inconsistently and sometimes incorrectly

- Excel uses poor algorithms for many functions

- Scripting is possible but rare

<img src="img_12/phd-comic-vcs.gif" alt="alt text" width="400">

- Lots of human effort for tedious & time-wasting tasks

- Error-prone due to manual & ad hoc data handling

- Difficult to record - hard to reconstruct a 'click history'

- Tiny changes in data or method require extensive reworking

- 2010: Claimed high debt-to-GDP ratios led to low GDP growth

- Threshold to growth at a debt-to-GDP ratio of >90%

- Substantial popular impact on autsterity politics

<img src="img_12/reinhart_rogoff_coding_error_0.png" alt="alt text" width="400">

<img src="img_12/reinhart_rogoff_econ_mag.png" alt="alt text" width="500">

Excel coding error sliced several countries out of the data set....

[The Economist](http://www.economist.com/news/finance-and-economics/21576362-seminal-analysis-relationship-between-debt-and-growth-comes-under)

[Source](http://retractionwatch.com/2013/02/01/seizure-study-retracted-after-authors-realize-data-got-terribly-mixed/)

Authors informed the journal that the merge of lab results and other survey data used in the paper resulted in an error regarding the identification codes. Results of the analyses were based on the data set in which this error occurred.

[Source](http://retractionwatch.com/2014/07/01/bad-spreadsheet-merge-kills-depression-paper-quick-fix-resurrects-it/)

<img src="img_12/open-science.png" alt="alt text" width="200px">

- Plain text files readable for a _long_ time

- Improved transparency, automation, maintanability, accessibility, standardisation, modularity, portability, efficiency, communicability of process (what more could we want?)

- Steeper learning curve

For example...

If I say that 2 + 2 = 4, why would you believe me?

```{r, cache=F, warning=F}

The text and R code are interwoven in the output. The products are ephemeral - focus is on the methods!

Of course `2+2` is trivial, but what if I said:

<img src="img_12/model.png" alt="alt text" width="800">

**Pros**

- Text & code in one place, in logical order

- Tables and figures automatically updated

- Automatic test when building document

**Cons**

- Text and code in one place; can be hard to read

- Can slow down the processing of documents (use caching!)

**Payoffs**

- Free space for hosting (and paid options)

- Assignment of persistent DOIs

- Tracking citation metrics

**Costs**

- Sometimes license restrictions (CC-BY & CC0)

- Limited or no private storage space

<img src="img_12/figshare.png" alt="alt text" width="30%">

<img src="img_12/dryad.png" alt="alt text" width="30%">

<img src="img_12/zenodo.png" alt="alt text" width="30%">

- **Good**: Use code with an integrated development environment (IDE). Minimize pointing and clicking (RStudio)

- **Better**: Use version control. Help yourself keep track of changes, fix bugs and improve project management (RStudio & Git & GitHub or BitBucket)

- **Best**: Use embedded narrative and code to explicitly link code, text and data, save yourself time, save reviewers time, improve your code. (RStudio & Git & GitHub or BitBucket & rmarkdown & knitr & data repository)

<img src="img_12/VictoriaStoddenIASSISTJune2010-reasons-to.png" alt="alt text" width="600">

<small>Stodden (IASSIST 2010) sampled American academics registered at the Machine Learning conference NIPS (134 responses from 593 requests (23%). Red = communitarian norms, Blue = private incentives</small>

<img src="img_12/VictoriaStoddenIASSISTJune2010-reasons.png" alt="alt text" width="600">

<small>Stodden (IASSIST 2010) sampled American academics registered at the Machine Learning conference NIPS (134 responses from 593 requests (23%). Red = communitarian norms, Blue = private incentives</small>

Reproducible Research Standard (Stodden 2009)

- The full compendium on the internet

- Media such as text, figures, tables with Creative Commons Attribution license (CC-BY)

- Code with one of Apache 2.0, MIT, LGPL, BSD, etc.

- Original "selection and arrangement" of data with CC0 or CC-BY

Promote culture change through positive attribution

Implement mechanisms to indicate & encourage **degrees of compliance** (ie. clear definitions for different levels of reproducibility), cf. Stodden's:

- **'Reproducible'**: compendium of text-code-data online

- **'Reproduced'**: compendium available and independently reproduced

- **'Semi-Reproducible'**: when the full compendium is not released

- **'Semi-Reproduced'**: independent reproduction with other data

- **'Perpetually Reproducible'**: streaming data

The machine-readable part: R

* R: Free, open source, cross-platform, highly interactive, huge user community in academica and private sector

* R packages an ideal 'Compendium'?

* Scriptability → R

* Literate programming → R Markdown

* Version control → Git / GitHub

<img src="img_12/markdown.png" alt="alt text" width="100">

Markdown: lightweight document formatting syntax. Easy to write, read and publish as-is.

The human-readable part:

- minor extensions to allow R code display and execution

- embed images in html files (convenient for sharing)

- equations

- `*` for bullet, `_` for underline

`knitr` - descendant of Sweave

Engine for dynamic report generation in R

<img src="img_12/knitr.png" alt="alt text" width="200">

- Narrative and code in the same file or explicitly linked

- When data or narrative are updated, the document is automatically updated

- Data treated as 'read only'

- Output treated as disposable

<img src="img_12/pandoc-workflow-rmd-md.png" alt="alt text" height="500px">

<small><small><small>http://kieranhealy.org/blog/archives/2014/01/23/plain-text/ </small></small></small>

A universal document converter, open source, cross-platform

* Write code and narrative in rmarkdown

* knitr->markdown (with computation)

* use pandoc to get HTML/PDF/DOCX

**Payoffs**

- Eases collaboration

- Can track changes in any file type (ideally plain text)

- Can revert file to any point in its tracked history

**Costs**

- Learning curve

<img src="img_12/git.png" alt="alt text" width="25%">

<img src="img_12/github.png" alt="alt text" width="25%">

<img src="img_12/bitbucket.png" alt="alt text" width="25%">

<img src="img_12/rstudio.png" alt="alt text" width="10%">

* integrated R console

* deep support for markdown and git

* package development tools, etc. etc.

* [Slides based on Ben Marwick's presentation to the UW Center for Statistics and Social Sciences (12 March 2014)](https://github.com/benmarwick/CSSS-Primer-Reproducible-Research) ([OrcID](http://orcid.org/0000-0001-7879-4531))

**References:** See Rmd file for full references and sources

```{r, echo=FALSE}