Reproducibility Standards in Economics (and beyond)

JHU FOSSProF Summative Event

Alan Lujan

Johns Hopkins University AAP

Chris Carroll

Johns Hopkins University

October 7, 2024

REMARK Motivation

  • Econ lags in reproducibility practices
  • State of field: for published papers
    • .zip archive has some files
      • rarely works ‘out of the box’
    • Top-5 journals have a ‘data editor’
      • Very expensive
      • Excellent barrier to competition
      • Data \(\neq\) results

Econ-ARK REMARK solutions

  • Standards for reproducibility of compute
    • self-contained and complete projects
    • executable on any modern computer
  • Emphasis on:
    • minimally good code
      • enforced algorithmically
      • would be huge improvement
      • “ChatGPT, fix my documentation”
    • explicit claims (“Risk Aversion: [2.5,3.5]”)
    • standardized metadata

So Far: About 23+3 REMARKs

Jointly Reproducible: Code and Math and Text

  • Solved: most computational aspects

Math and Text with Code?

  • \(\LaTeX\) is standard for text, but…
    • definitely not lightweight
    • no dynamically executable content
  • Now: tenuous connection between text and code
    • “where is equation 18 implemented”?
      • in a gestalt of interactions
  • Future:

FOSSProF \(\rightarrow\) Curvenote

Funding let us hire open source contractor - To do things we could not do

At our direction:

  • Integrated MyST Markdown into REMARK
  • Filled gaps in tools to integrate text, math, and code
  • Improved \(\LaTeX\) \(\rightarrow\) MyST engine
    • Tools required for some of our REMARKs

Curvenote: \(\LaTeX\)

Curvenote: Computation

Journal of Open Source Economics

Not Specific to Economics!

  • conceived for projects using Econ-ARK
    • … but doesn’t require Econ-ARK
  • Not bound to economics in any way

Rebranding: REMARK \(\rightarrow\) SCI-PASS

  • Scholarly Communication Infrastructure for Publishing and Archiving Scientific Software
  • Ambition:
    • universal standard for repr compute
      • nothing now exists (we’ve looked)
  • Also short for “scientific passport”
    • portability/sharing of research outputs

Long-Term Goal: ISO standard

  • Adoptable by journals, libraries, archives …
  • Existing software standards got started this way
    • Somebody needed it for their own purposes
  • Members of our team:
    • SB: “Information Science” PhD
      • connection to archivists, librarians
    • AS: Economics PhD
      • Vetted ISO software standards for Oz