Measurements#
PhenoTypic writes its results as tables. This reference documents every column that appears in them, grouped by the operation that writes it: one page per measurement operation and per analyzer, listed in the sidebar by stage. Each column carries a Type badge that says how far a single value can be trusted; the Tier System page explains the badges.
Reading a measurements table#
Each row of deliverables/measurements.csv describes one detected colony. Its columns come in four blocks, always in this order:
Your experimental metadata, from the
--metadatafile: strain, condition, replicate and the like (Metadata_Strain). See Metadata.Measurements, one block per measurement operation in pipeline order. Every column name starts with its metric family:
Size_Areais in the Size family and is written by MeasureSize.Image bookkeeping: the image each colony came from (
Metadata_ImageName,Metadata_BitDepth).Where the colony is:
Object_Label, its bounding box (Bbox_*) and, on gridded plates, its well (Grid_*). See Shared columns.
Where tables are written#
A CLI run writes these files under its output directory:
File |
One row per |
Holds |
|---|---|---|
|
detected colony |
every measurement column, with your metadata joined |
|
detected colony |
one measurement operation’s columns, plus the metadata and position columns |
|
detected colony |
one category’s columns, plus the metadata and position columns |
|
one table per quality check |
each check’s columns; see Quality control in the sidebar |
|
fitted group |
the pipeline’s growth-model parameters and fit metrics |
|
curated colony |
the category you assigned in the results viewer |
Analyzers you run yourself return the same columns from analyze().
Reading an operation page#
Every operation page has the same parts:
A one-line summary of what the operation measures, and a link to its parameters.
The table’s facts: what one row describes, where the table is written, and how many columns the operation adds.
One column table per schema, listing each column exactly as it is written. Where a header embeds the analyzed column, the page shows a placeholder (
<metric>) and an example.
Operations#
Operation |
Stage |
What it writes |
|---|---|---|
Object measurements |
Extract bounding box coordinates and centroids of detected colonies. |
|
Object measurements |
Measure robust colorimetric statistics for each colony. |
|
Object measurements |
Evaluate grid alignment quality using row-wise and column-wise linear regression. |
|
Object measurements |
Quantify within-well colony dispersion using pairwise centroid distances. |
|
Object measurements |
Measure grayscale intensity statistics of detected colonies. |
|
Object measurements |
Measure distances to grid neighbours and to the nearest object. |
|
Object measurements |
Measure absolute and radial-relative hyphal orientation by growth zone. |
|
Object measurements |
Measure the form of each detected colony. |
|
Object measurements |
Measure the key size magnitudes of each detected colony. |
|
Object measurements |
Measure colony radial expansion, symmetry, and canonical radial zones. |
|
Object measurements |
Measure colony surface texture using Haralick features from gray-level co-occurrence matrices. |
|
Quality control |
Flag groups whose detected colony count diverges from metadata. |
|
Quality control |
Flag groups whose grid occupancy (filled cells / expected) is low. |
|
Quality control |
Flag |
|
Quality control |
Flag |
|
Quality control |
Flag |
|
Quality control |
Flag |
|
Quality control |
Flag |
|
Growth models |
Linear-softplus growth fitter with a softplus saturation ceiling. |
|
Growth models |
Linear-with-softplus lag-phase growth fitter (no saturation). |
|
Growth models |
Logistic-growth model fitter with regularized least-squares objective. |
|
Plate correction |
Analyzer for detecting and correcting edge effects in arrayed colony growth. |