Understanding FCS metadata before editing
Inspect file metadata and measurement-channel definitions before making a working copy.
FCS Editor
Practical notes for a careful workflow.
Start with file inspection, preserve originals and make compatibility claims specific to a release.
Learning center · Release notes
What is inside an FCS file?
An FCS file combines descriptive metadata with event measurements. Channel parameters describe the measurements, while keywords identify acquisition and file-layout information. A filename or plot alone does not establish the file’s provenance.
Before editing, review the channel definitions, event count and metadata. Keep the source acquisition file unchanged and compare a working copy against it.
How should edited FCS data be documented?
Keep the original, save the output separately and record the software version, operation, affected channels or events and purpose. Synthetic events or modified values require explicit labeling. Editing a file does not create new experimental observations.
What does compatibility mean?
Compatibility depends on FCS layout, channel parameters, compensation metadata and the consuming application. A successful read is distinct from a verified write-and-reopen workflow. Workspace gate import also requires checking the displayed geometry and event membership.
A formal release-specific compatibility table will be published after the online package is validated. No universal vendor compatibility is claimed.
Keep learning
Product capabilities and limits · Real software demonstrations · Installation and activation basics
Public workflow articles
Preserving originals in an FCS editing workflow
Keep the acquisition file, describe each operation and distinguish generated values from observations.
Checking FCS and workspace compatibility
Separate successful file reading from a validated write-and-reopen or workspace import.