Exporting

Exporting requires a license.

Statistics as CSV

The statistics table exports as CSV — one row per population, with counts, frequencies and per-channel statistics.

For an experiment rather than a single sample, use the batch route: one table with a row per sample. See Batch analysis.

Event data as CSV

Three scopes:

Scope	What you get
All events	Every event in the active file
One gate	Only events inside the population you pick
Batch	All events across every selected file

Per-gate event export is the route to another tool — hand the events for a population to R or Python without re-deriving the gate there.

Event exports are large

An event-level CSV of a million-event file is a big text file, and a batch export across an experiment is much bigger. Export the population you need rather than everything, when you can.

Figures

Plots export as SVG, PDF or PNG.

• SVG for figures you will edit in Illustrator or Inkscape — it stays sharp and the elements remain separable.
• PDF for direct inclusion in a manuscript.
• PNG for slides and quick sharing.

Prefer SVG or PDF for anything going into a publication. A raster screenshot of a scatter plot loses exactly the sparse events that are usually the point.

The compensation matrix

The spillover matrix exports for the record. Do it.

What makes a result reproducible

A statistics table on its own does not record how it was produced. For a figure or number you may need to defend, export:

1. The statistics — the numbers themselves.
2. The compensation matrix — the transform applied to the data.
3. The workspace — gates, hierarchy, scales and axes. See Workspaces.
4. The AI audit trail, if the copilot was involved — which steps were proposed and which you approved.
5. The AI-1 competence report, if AI-1 gated anything — including which populations it declined.

Points 4 and 5 are the ones people forget, and they are the ones a reviewer asking “how was this gated?” is actually asking about.