render op• Data kinds: labels → table
• Call: import fullseye as fs; fs.ledger.vol_labels_to_meshes(labels, ids=None, spacing=None, seed: 'int' = 0, level: 'float' = 0.5, axes: 'str' = 'xyz') (to call the implementation directly, import volcolor; volcolor.vol_labels_to_meshes(labels, ids=None, spacing=None, seed: 'int' = 0, level: 'float' = 0.5, axes: 'str' = 'xyz'); from the registry, opsvolcolor.get("vol_labels_to_meshes"))
Run marching cubes per component, giving a set of coloured meshes.
Returns list[dict], each element being {"label", "vertices" (nv, 3) float64, "faces" (nf, 3) int64, "color" (r, g, b)}. The colours use the same palette as vol_colorize_labels, so in section views and in the 3-D display the same part has the same colour.
Per component, only the sub-volume of the bbox padded by 1 voxel is cut out and marching cubes is run on it (it does not sweep the whole volume once per component). The padding closes the surfaces of components touching the volume edge; without it, only the edge components become meshes with holes.
axes:
• "xyz" (default) -- returns vertices as (x, y, z). This is the vertex order of render3d / mesh, so they can be passed straight to render3d.render_mesh.
• "zyx" -- returns them in the volume's index order. This matches the order of centroid in vol_label_shape_stats.
Mixing them up silently raises no exception -- what comes out is a plausible picture with up/down and front/back
swapped. tests/test_volcolor.py::test_mesh_axes_order_is_explicit
pins this by checking both centroids against the stats centroids.
Passing *spacing* gives vertices in physical coordinates (mm). *ids* narrows the components (None means all labels that exist, but at most MAX_MESHES).
Raises ImportError (with the pip install scikit-image message) when marching cubes is unavailable, and ValueError for a bad *axes*, a *level* outside (0, 1), an *ids* naming an absent label, or more than MAX_MESHES components.
• 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.
• The canonical algorithm (author, year) and its uses are named in the family usage guide above.
• voxel_labels_color — py -3.11 examples/voxel_labels_color.py
table as input)—
render)*Provenance: volcolor.py — VOLCOLOR 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.