Not every replication package can be run on SIVACOR. This page helps you make that assessment before going forward.
Available software¶
SIVACOR can only run the software listed below. Your replication package must be able to run with one (or a sequence) of these. See Available Software for the specific versions available for each.
Ability to separate code into discrete software steps¶
Each step of a SIVACOR submission only supports a single software application (Stata, R, MATLAB/Dynare or Julia — see Available Software). While it is possible to chain multiple software steps in sequence (see instructions in Step 2), SIVACOR does not currently support call one application from another (e.g., call R from Stata, or Julia from `MATLAB). If your code iterates frequently between applications, for instance in a loop, you cannot use this system.
It can, however, be used when a small number of actions are needed in one software application, with the bulk in a main application. For instance, if you use Stata for data preparation, but R for all remaining analysis, your package can be handled by SIVACOR.
Do not include any data that you are not allowed to upload to third-party systems¶
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.[1] You should not upload controlled data, and all uploads should be compatible with any data use agreement you signed.
If you have data that you are allowed to upload, but not publish, see next section and “Excluding files” on how to exclude files from the final replication package.
Do include data that you can upload but not publish¶
By default, the final digitally signed replication package (TRO) contains all data as originally uploaded. You should not make manual modifications afterwards, as that will break the integrity of the package (see Checking Integrity of Your Replication Package). But you can configure SIVACOR to transparently remove the files for which you do not have redistribution rights. This will be logged as part of the TRO.
Package must be able to fit on the SIVACOR workers¶
The size available to run your code depends on the software being used, and how you manage files within your replication package. A complete run of your code needs room:
the operating system
the statistical software you use
multiple copies of your replication package:
the ZIP file you upload
the workspace it is extracted into
anything your code writes
Current SIVACOR nodes have between 23 and 44 GiB free, depending on the software being used.
Additional planning information
This instance of SIVACOR launches a virtual machine for each run. Its disk is advertised as 60 GB; once formatted the filesystem measures 58 GiB, which is the figure every number below is in. Of that, about 12.7 GiB is the operating system and the SIVACOR harness. Roughly 45 GiB are available before the analysis software is added. Software sizes differ a great deal, and the software is unpacked onto the same disk your package lives on.
The table below lists what is left for your package after each one. See Available Software for the full, curated list.
* Estimated from the compressed download size.[2]
For more information on the system itself, see Hardware capabilities.
A run is stopped if the worker runs out of disk space, see the FAQ.
If your package cannot be made to fit the free space in the table above, you may be able to ask for extra scratch disk.
The next step is to prepare your package.
ℹ️ FAQ¶
See the FAQ.
SIVACOR runs on Jetstream2 infrastructure. The JS2 Acceptable Use and Data Policy apply. SIVACOR’s privacy policy can be found at https://
submit .sivacor .org /privacy. The software is kept both compressed and unpacked on the worker’s disk, so it occupies roughly 3.5x what it downloads.