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.

Downloading Results

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

Once the job is finished, the submission page reports the outcome and offers the files the run produced.

Job finished

After a successful run

You can now download the Replicated Package, a ZIP file that contains your originally submitted materials, the output files generated by your code, and the TRACE-related files (TRO Declaration, TRS Signature, Trusted Timestamp, see FAQ) that prove that this job was run on SIVACOR.

SIVACOR output files

The components can also be individually downloaded.

You can also download a Workflow definition — a small YAML file describing the software, versions and main files this run used. It is not part of the signed . It can be used to reproduce the same setup later by importing it on the submission page, instead of filling the form in by hand (see Optional chained runs).

After a failed run

Failed run

A failed run does not produce a signed package, only the Run output log and the Run error log. Download those to inspect the detailed reason for failure.

Log files

Read the error log first: it will list the command, file or package at fault. The debugging guide covers common ones per software. The FAQ also covers failures that are system faults, not package faults.

Keeping and deleting results

Handing the package to a journal

ℹ️ FAQ

See the FAQ.