EpistaBase Docs
Apps

Flow

Build and review flow cytometry workspaces with gates, sample context, and population statistics.

guideReviewed 2026-06-26

The Flow app is EpistaBase's focused environment for flow cytometry. Use it when you need saved gating work, not just a quick scatter preview.

EpistaBase Flow app screenshot
Flow workspaces store samples, gate trees, plot settings, compensation state, and population statistics.

What a Flow workspace contains

PartWhat it does
SamplesParsed FCS files attached to the workspace.
PlotScatter, histogram, density, pseudocolor, or overlay view.
ChannelsFCS channel labels and markers extracted during parsing.
GatesA hierarchy starting from locked All events.
StatisticsCounts, percent parent/total, and selected channel statistics.
Template stateSaved hierarchy and settings that can be reused.

Open a Flow workspace

  1. Open Flow.
  2. Open the workspace you want to review.
  3. Select one sample.
  4. Inspect the gate tree from All events to the population of interest.
  5. Read the statistics table for the selected gates and samples.

Draw and edit gates

Flow supports drawing gate types directly on the plot, including rectangle, polygon, ellipse, threshold/range, quadrant-set, and boolean gates. The root gate is locked so the tree cannot lose its base population.

Use names that describe the biological population, not the drawing operation:

BetterAvoid
Cellsrectangle 1
Singletsgate copy
Annexin V / PI hightop right

Read population statistics

Population statistics use the same gated event basis as the plot. Common columns include:

  • event count
  • percent of parent
  • percent of total
  • mean
  • median
  • geometric mean
  • coefficient of variation

Statistics export includes workspace, sample, gate, channel, statistic, and value context so exported results can still be interpreted.

Save and publish

Edits are saved with the workspace. When the gating strategy is ready to share, publish the workspace so collaborators can return to a stable analysis state instead of a moving draft. Treat published Flow workspaces like a methods result: name gates clearly, check the statistics, then link the published output from the project report or analysis.

On this page