vol_rle_components — 3D rle_region op

• Data kinds: voxel → rle_region

• Call: import fullseye as fs; fs.ledger.vol_rle_components(vol_binary, connectivity=26) (to call the implementation directly, import volregion; volregion.vol_rle_components(vol_binary, connectivity=26); from the registry, ops3d.get("vol_rle_components"))

Usage

Split a binary volume into per-component `VolRLE` regions.

*The* use case run-length regions exist for: holding every component of a

segmentation as its own region at run-proportional cost, instead of one

dense label volume or N dense masks. Uses the key structural fact that a

run is x-connected, so a component label is constant along each run — the

volume is labelled once (dense, same 6/18/26 semantics as

`volops.vol_label`) and then each *run* is assigned by its first voxel's

label; no per-component dense mask is ever built.

Returns a list of `VolRLE` ordered by label id (1..n). An empty mask

returns an empty list.

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

Runnable examples (verified samples that actually call this op)

• rle_region_efficiency — py -3.11 examples_3d/rle_region_efficiency.py

Ops the type connects to (they accept rle_region as input)

vol_rle_decode · vol_rle_volume · vol_rle_bbox · vol_rle_centroid · vol_rle_union · vol_rle_intersect · vol_rle_difference · fuse_to_voxel

Same category (rle_region)

vol_rle_encode · vol_rle_decode · vol_rle_volume · vol_rle_bbox · vol_rle_centroid · vol_rle_union · vol_rle_intersect · vol_rle_difference

*Provenance: volregion.py — 3D operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.