Output formats#

The structure and formats for experiment results and Kiso’s own output files.

Output directory structure#

Kiso writes all output to the directory specified by --output (default: output/).

output/
  env                       ← EnOSlib environment state (used by kiso up, kiso run, and kiso down)
  <files-or-directories>    ← Files or directories specified in the `outputs` section of the `shell` experiment config.

Pegasus workflow output#

For Pegasus experiments, the output structure includes the Pegasus execution directory:

output/
  <experiment-name>/
    <instance-0>/
      <submit-dir>/
        statistics/
        analyzer.log        ← success/failure analysis
        other pegasus files ← Pegasus execution directory contents

The Pegasus execution directory contains Pegasus-native files: braindump.yml (workflow metadata), monitord.log, individual job logs etc.

File transfer outputs#

Files specified in the outputs section of an experiment are downloaded to the local path specified by dst. There is no imposed format — files are transferred as-is from the remote node.

Config example:

outputs:
  - labels: [compute]
    src: /scratch/results/data.csv
    dst: local-results/

Result:

local-results/
  data.csv

Environment state file (env)#

The env file is a pickled Python object containing EnOSlib environment state. It is used internally by kiso up, kiso run, and kiso down to reconnect to provisioned resources.

This file is not intended for direct use. Do not modify it. It is specific to the provisioned resource set and becomes invalid after kiso down.

See also#