4  Numerical Feature Extraction

Open Data Extraction → Numerical in a local installation to turn a folder of input files into a single-cell feature table. This one workflow checks the inputs, prepares the FOV metadata, calibrates the channels that need it, and extracts and saves the numerical features based on configured per-channel feature extractors.

4.1 Field of View Metadata

See Field of View Metadata for FOV search by scanning a user-provided folder, file validation, channel assignment, acquisition checks, and the automatically saved metadata record.

4.2 Calibration interface

Interactive calibration is needed only for some use cases. See IRF Calibration for FLIM shift calibration and QPI Background Correction for QPI calibration.

After the folder is scanned, the next button reflects whether the selected extractors need interactive calibration:

  • Start calibration prepares channels that need an IRF shift or QPI background correction.
  • Start extraction prepares and immediately extracts when no interactive calibration is needed, for example an intensity-only workflow.

4.2.1 Review each channel that needs calibration

Channel and selected extractor Calibration to review
Raw FLIM with Lifetime fit Reconvolution fitting and IRF shift, including fitting options and time gates
FLIM with Lifetime fit free and IRF calibration IRF shift; a raw lifetime fit supplies its fitted shift when both extractors are selected
QPI with Dry-mass statistics or Spatial texture Background correction for that channel

For FLIM shift calibration, review the left-hand settings and click Optimize for Shifts. In a workflow that also requires QPI correction, this button is Calibrate channels. QPI-only background calibration opens directly after Start calibration.

Fluorescence lifetime standard calibration is applied during phasor extraction. It does not require an interactive IRF shift unless that channel also performs raw lifetime fitting. A QPI channel selecting only morphology does not require background calibration.

When every required channel is ready, click Confirm calibration for each channel. Confirmation automatically updates the same metadata record with the chosen settings.

4.3 Feature Extraction

After confirming calibration, raw FLIM channels using Lifetime fit default to Local fitting. Leave it selected for faster cell-level fitting or change the mode using the mode guidance, then click Start extraction. To revisit calibration, use Go back and find shift, Go back and correct background, or Go back and recalibrate, as appropriate for the channels.

Confirmed calibration with Fitting Mode set to Local by default and buttons to start extraction or return to shift calibration.

After confirming calibration, choose the fitting mode and start extraction.

The selected extractors provide:

Configured derived features are calculated after the successful FOV results are combined.

The right side lists FOVs and their extraction status. Progress bars appear during processing, and completed FOVs show their result badges. Keep the page open while the batch runs and check any errors or warnings before using the output.

Numerical workflow showing Fitting Mode set to Local by default, per-field-of-view extraction progress, and result badges.

Follow per-FOV progress and results during numerical extraction.

Cells with missing feature values (NaN) remain in the exported table; the app reports warnings about those values.

4.4 Save Results

The completed table is automatically written as single_cell_features_<timestamp>.csv in the source folder. The page shows a preview and the saved path.

Completed numerical extraction with a cell-feature table preview and a successful export message showing the local CSV path.

Inspect the extracted table and its automatically saved CSV path.

If saving the features fails, correct the reported problem and click Retry exporting features. This saves the already calculated table without rerunning extraction. The metadata CSV remains a record of the input files, extraction settings, and confirmed calibration; the workflow starts from a source folder on each new run.