Compute stats
Overview
Parses a dataset’s annotations once and stores what they contain — object classes, geometries, areas, box sides, and tags — as columnar files in workspace storage. Other nodes, such as Data Quality Control and Filter images, read those files instead of downloading and parsing the annotations again.
Statistics are keyed to the annotation, and annotations are immutable, so every annotation is parsed once ever. A rerun over an unchanged dataset computes nothing, and datasets that share annotations — copies, splits, merges — share the stored rows.
Running this node is never required: consumers compute whatever the store is missing on their own. Place it in a flow to pay the one-time parsing cost up front, for example on a schedule or before a large filtering step.
How it works
FAQ
Do I have to run this node before Filter images or Data Quality Control?
No. Consumers compute whatever the store is missing on their own. Running this node first only moves the one-time parsing cost to a moment you choose.
What happens when annotations change?
Editing labels produces a new annotation with a new id, so the next run computes rows for the new annotations only. Rows of annotations that left the dataset stay in the store, and consumers ignore rows that no current annotation refers to.
Why does the badge show 0 computed?
Why does the badge show 0 computed?
Every annotation of the dataset is already in the store. That is the normal state after the first run.
Inputs
Dataset whose annotations are measured. Annotations measured by an earlier run are skipped, so a rerun over an unchanged dataset does no work. Key: DATASET.
Outputs
How many annotations were computed on this run. Shown on the node as a badge. Key: STATS_SUMMARY.
JSON config
Machine-readable node interface for automation and advanced usage.