Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Preparing a Compatible Replication Package

Authors
Affiliations
Cornell University
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign

You should not include any data that you are not allowed to share publicly.

While SIVACOR does not publish data or replication packages, and deletes completed jobs after a short period of time, it is not a designated secure computing system.

Your replication package should be portable.

Code must run without manual intervention, use a single controller script (e.g., main.do or master.R), and avoid hard-coded absolute paths. You can only upload the package, not edit it on the site. It should also not have inconsistently used case-sensitive file or directory names.

All dependencies must either be included or installed automatically.

If your code uses libraries or packages, you must ensure that they are installed automatically. We strongly encourage packages that use “environments”, and packages to manage dependencies, such as renv for R.

Your replication package only uses a single software application.

Each run of SIVACOR only supports a single software application (e.g., Stata, R, Python), as encapsulated by containers. If your replication requires multiple applications, you will need to configure separate runs. However, your package itself can include the code for multiple applications.

Prepare a ZIP or tar.gz file

Your replication package must be a single ZIP file or tar.gz file.

The next step is to upload your package to SIVACOR.