3 Configuration
Configure FLIM Playground once and it is applied to future data. You can keep up to 10 named configuration profiles and switch between them for different experiments.
Configuration has two levels: settings shared by the experiment and settings chosen for each channel. For a mixed-modality experiment, assign a modality to every channel first, then complete the input and extractor settings for each channel.
3.2 Configure each channel
3.2.1 Channel Name
Customize each channel name, for example with the fluorophore name.
3.2.2 Imaging Modality
Choose one modality for each channel:
| Modality | Use it for | Input formats |
|---|---|---|
FLIM |
Time-resolved signals | 2D decay (.csv), 3D/4D decay (.sdt, .ptu), or 3D/4D pixel pre-fit (.asc) |
Intensity-only |
2D intensity images without a time axis | .tiff, .tif, .asc |
QPI |
2D optical path difference images | .tiff, .tif, .asc |
FLIM input format
Choose one format for the FLIM channels in this profile. The detailed file description is grouped below so that you can open only the format you use.
A 2D decay CSV contains one cell per row and one time bin per column. It must be headerless and numeric. Do not include identifier or annotation columns. Because each row already represents a cell, no mask is required.
A profile using 2D decay CSVs cannot include QPI or intensity-only image channels. Use an image-based FLIM input format for a mixed-modality workflow.
3D/4D decay stores spatial dimensions and a time dimension; an optional additional dimension represents acquisition channels.
.sdt: Becker & Hickl.ptu: PicoQuant/Leica
The app reads duration and time-bin information from the acquisition metadata. Repeated PTU frames are summed into one decay image per FOV. For a time-lapse acquisition, split the data into one file per time point before extraction.
Use pixel pre-fit inputs when lifetime fitting was performed in SPCImage. FLIM Playground aggregates the pixel features inside each cell mask.
.asc: a 2D spatial array containing one lifetime feature value per pixel, such ast1.- Additional component and fraction files are inferred from the
t1filename by replacingt1witht2,t3,a1[%], and so on.
The mask is required for cell aggregation. Fixed-lifetime controls are not shown because the lifetimes are read from the pre-fit files.
3.2.3 Feature Extractor
Choose extractors according to the measurements you need:
| Measurement goal | Extractor | Applies to |
|---|---|---|
| Fit lifetime components and fractions | Lifetime fit | FLIM raw decay or pixel pre-fit |
| Phasor coordinates and fit-free lifetimes | Lifetime fit free | FLIM decay |
| Cell shape measurements | Intensity Morphology | Image-based FLIM, intensity-only, or QPI |
| Intensity texture | Intensity Texture | Image-based FLIM or intensity-only |
| Dry mass and mass-distribution statistics | Dry-mass statistics | QPI |
| QPI spatial texture | Spatial texture | QPI |
Lifetime fit settings
When Lifetime fit is selected, choose the number of lifetime components to fit.
Raw FLIM inputs also require an IRF and a confirmed IRF shift calibration before fitting. Pixel pre-fit inputs do not require this fitting-based calibration because their lifetime values are already provided.
Provide one IRF per channel in .txt, .csv, or .ptu format.
When the number of components is greater than one, open Advanced: fixed lifetimes to set known component lifetimes in nanoseconds. Set a component to 0 to leave it free for optimization. These values become defaults for the interactive fitting phase and are unavailable for pixel pre-fit inputs.
Lifetime fit free settings
When Lifetime fit free is selected, set the laser frequency in MHz and choose a calibration method:
IRF: use a per-channel IRF and complete IRF shift calibration.Fluorescence Lifetime Standard: use a per-channel standard file and enter the shared standard lifetime in nanoseconds.
For Fluorescence Lifetime Standard calibration, provide a .tiff, .tif, or .ptu reference file.
See the fit-free calibration settings for the correction applied by each method.
QPI settings
When QPI is selected, set these physical constants for the channel:
- Pixel size (µm): the specimen distance represented by one image pixel after binning. It must be positive; there is no default. The app uses its square as the pixel area.
- OPD unit in file: choose
m,um, ornm. The file must already contain optical path difference, rather than an unconverted phase angle. This choice is required; there is no default. - α (µm³/pg): the specific refractive increment used for dry-mass conversion. It defaults to
0.181818µm³/pg and must be finite and greater than zero.
Selecting Dry-mass statistics or Spatial texture also requires a confirmed background correction. The QPI channel’s image and mask suffixes are set in File Suffix, and the mask requirements are described in ROI Mask.
3.2.4 ROI Mask
All image-based channels require a cell-level ROI mask: FLIM (3D/4D decay or pixel pre-fit), intensity-only, and QPI. Channels can share a mask or use different masks; when masks differ, the integer label for the same cell must match across them. Each image must match its own mask dimensions.
.tiff/.tif: a 2D array with background labeled0and each cell ROI labeled with a unique positive integer. The label becomes part of the cell identifier.
Every pixel carrying the same integer forms one cell, even when those pixels are in separate regions. If one label covers two cells, their pixels are treated as one cell for feature extraction; relabel the mask when they should be measured separately.
3.2.5 File Suffix
Source preparation in Numerical finds files using the configured suffixes. The selected modality, decay type, calibration method, and extractors determine which suffixes are required. Additional SPCImage component suffixes are inferred from the t1 suffix.
Choose suffixes that identify each input unambiguously in the folder you will scan. A shared mask suffix can be used when channels measure the same cell ROIs. The FOV Metadata reference explains how suffixes are matched to FOVs and calibration references.
3.3 Derived Features
The Derived features builder composes new single-cell features by arithmetic over the features you extract, optionally combining operands from different channels. Definitions are saved with the current profile and computed during Numerical Feature Extraction.
3.4 Save
Click Update Configuration to save the current profile. If FLIM Playground is open in more than one browser tab, another tab showing Data Extraction will display a notice asking you to reload before using the new settings.





