Skip to content

Instantly share code, notes, and snippets.

@korenmiklos
Created June 3, 2021 20:58
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save korenmiklos/8b7ffcf4f2f71fcb33e255659e90347c to your computer and use it in GitHub Desktop.
Save korenmiklos/8b7ffcf4f2f71fcb33e255659e90347c to your computer and use it in GitHub Desktop.

Replicability Manifesto

  1. Cite everything that the replication package relies on.
    • Why: Citations in the manuscript and the README are the best way of directing readers to these resources and to give credit to the original authors.
    • How: All datasets, whether public or private, included or not, should be cited. It is good practice to cite software packages, but not required, unless the license terms specifically ask you to do so.
  2. Include all exhibits and the code to produce them ALL DATA THAT YOU ARE ABLE (drill down).
    • Why: The package should be self contained so that readers can verify that your analysis code produces the output you included.
    • How: Save all the output of the analysis in some standard format into the replication package. Tables can be saved as .csv, .xls or .tex files. It is also sufficient to save the Stata .log file. In this case, please report in the README the line numbers where the readers can find the table numbers. Figures can be saved in .eps, .pdf or .png.
    • How 2: Refer to confidential data questionnaire.
  3. For files not included, explain how to get them.
    • Why: The goal is to describe clearly the steps that readers have to take if they want to access the data and software you could not included.
    • How: Include a formal Data Availability Statement for each of the datasets you are using. List all software packages, libraries, toolboxes that you use in the README with instructions on how to install them.
  4. Guide the reader on how to get from the data to exhibits.
    • Why: Readers are expert empirical economists but need specific instructions on how to reproduce your analysis.
    • How: Create a list of exhibits and state which one is produced by which script. If possible, include a master script executing all the necessary steps. Explain if your code requires special hardware or runs for particularly long.

Notes to self

This is about “sharing research in a reproducible way.” As opposed to “doing research in a reproducible way.”

We need 3-4 full, worked-out examples. The complete READMEs. But we also want to show pieces of these examples.

People only care about rules as they apply to them. Almost no-one wants to read a complete rulebook. Show rules in context.

Topics are not optional, they hang together. So all 4-5 topics should be shown on the same page, with anchors at the respective topic headings.

Our audience is authors, not editors.

Promoting an open research culture | Science TOP Guidelines

[[Reproducible Standards]] [[Blog post ideas related to coding and reproducibility]]

#share #coded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment