A standard for ensuring computational reproducibility, archiving, and sharing of research projects.

REMARKs are self-contained projects that can, in principle, be executed on any modern computer.

The standard is focused on 3 key principles:

• Portability: The ability to move the project to an entirely different platform and be sure it will still work
• Archiving: Storing the project in an accessible format for future use and reference.
• Publishing: Sharing the project publicly to encourage transparency, collaboration, and incentivize code and data sharing.

Detailed technical instructions for using an existing REMARK or contributing a new REMARK can be found in How-To-Make-A-REMARK.md in this directory.

Types of content include (see below for elaboration):

1. Explorations
   • Use the Econ-ARK/HARK toolkit to demonstrate some set of modeling ideas
2. Replications
   • Attempts to replicate important results of published papers written using other tools
3. Reproductions
   • Code that reproduces ALL of the results of some paper that was originally written using the Econ-ARK toolkit

A catalog of all REMARKs is available under the REMARK tab at econ-ark.org. (Direct link: https://econ-ark.org/materials/?select=REMARK)

The ballpark is a place for the set of papers that we would be delighted to have replicated in the Econ-ARK. But we would welcome submissions of replications from any field of economics that requires meaningful computation.

In cases where the replication's author is satisfied that the main results of the paper have been successfully replicated, we expect to approve pull requests for new REMARKs with minimal review (subject to the criteria described in the Standard.

We also expect to approve with little review cases where the author has a clear explanation of discrepancies between the paper's published results and the results in the replication attempt.

Replication archives should contain two kinds of content (along with explanatory material):

1. Code that attempts to replicate key results of the paper
2. A Jupyter notebook that presents at least a minimal set of examples of the use of the code.

This material will all be stored in a directory with some short pithy name (a bibtex citekey might make a good directory name).

Code archives should contain:

• All information required to get the replication code to run
  • Including a requirements.txt file explaining the software requirements
• An indication of how long it takes to run the reproduce.sh script
  • One some particular machine whose characteristics should be described

Jupyter notebook(s) should:

• Explain their own content ("This notebook uses the associated replication archive to demonstrate three central results from the paper of [original author]: The consumption function and the distribution of wealth)
• Be usable for someone wanting to explore the replication interactively (so, no cell should take more than a minute or two to execute on a laptop)

The key difference with the contents of the DemARK repo is that REMARKs are allowed to rely on the existence of local files and subdirectories (figures; data) at a predictable filepath relative to the location of the root.