Skip to content

Exporting Analyses

Bulk Export can include analysis outputs alongside the original acquisition and session files in an export.

Added in version 22.4.0

Support for exporting analyses was added in Flywheel Core version 22.4.0.

What an Analysis Export Contains

When analysis export is enabled, the export can include:

  • Analysis output files — the files a gear job produced, along with any other derived data.
  • Analysis input files — the files the analysis consumed.
  • Analysis metadata — the gear name, gear version, inputs, and parameters recorded for each analysis.

Enabling Analysis Export

Analysis export is opt-in and is configured on the export rule. An export configured without this option contains only the original acquisition and session data, exactly as in earlier releases.

Analyses can also be filtered, so that an export includes only the analyses relevant to it rather than every analysis attached to the exported containers.

For where these options appear when starting an export, see Bulk Export Settings.

Destination Folder Structure

Exported analyses are written to an ANALYSES folder in the destination, organized by analysis label. Each analysis label contains separate INPUTS and OUTPUTS subfolders:

1
2
3
4
ANALYSES/
└── <analysis label>/
    ├── INPUTS/
    └── OUTPUTS/

Separating inputs from outputs keeps the files an analysis consumed distinct from the files it produced, so that a downstream consumer can tell derived data apart from source data.

Relationship to fw sync

Bulk Export replaces the fw sync command in the Legacy CLI (fw), including for exporting analysis results.