typed op• Data kinds: points → signal
• Call: fullseye.apply(img, "tb_env_studio", a=0.5, b=0.5) (the 2-D model is one image plus two scalar knobs a,b∈[0,1])
*The figure is the actual output on a synthetic 128×128 input. Left: input, right: output. Point clouds are drawn as a top-down scatter (brightness = z), 1-D series as a line plot, volumes as the maximum-intensity projection along z, videos as the middle frame, complex images as magnitude; return values that are not pictures are shown as the values themselves.*
*Knob a does not change the output (measured: identical at 0.1 / 0.5 / 0.9).*
Sweeping knob b (0.1 / 0.5 / 0.9, the other knob at its default):
▸ tb_env_studio: knob b sweep (docs site)
Stages (the ops that come before → this op, left to right):
▸ tb_env_studio: stages (docs site)
On other images (synthetic scene / photo / coins. Top row: inputs, bottom row: their outputs. Knobs at default):
▸ tb_env_studio: other inputs (docs site)
Radiance of a studio environment (direction -> brightness). Achromatic.
2 softboxes + a sky gradient + a thin horizontal band. It is left uncoloured to guarantee within the picture that the metal's colour comes from Fresnel(n, k), not from the environment. directions are (..., 3) unit vectors (z up). The return value has that shape, (...,).
The optics op env_studio bridged into the 2-D evolution registry. The implementation is the same; only the calling convention is adapted to op(v, a, b). a sweeps key (default 12) and b sweeps fill (default 3.2).
• 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 program below has been verified to run (same input as the figure). In Studio's help this block becomes buttons that load and run it on the spot.
img_to_points 0.50 0.50 tb_env_studio 0.50 0.50
▸ Load this pipeline · Load & run
The examples below call the underlying ledger op env_studio. This bridge op is the same implementation adapted to the fn(v, a, b) convention, so the behaviour carries over unchanged (only the call form differs).
• studio_raytrace_scene — py -3.11 examples/studio_raytrace_scene.py
signal as input)identity · tb_create_funct_1d_array · tb_smooth_funct_1d_gauss · tb_smooth_funct_1d_mean · tb_derivate_funct_1d · tb_integrate_funct_1d · tb_zero_crossings_funct_1d · tb_abs_funct_1d
typed)tb_points_to_voxel · tb_estimate_point_normals · tb_iss_keypoints · tb_project_points · tb_render_point_depth · tb_statistical_outlier_removal · tb_radius_outlier_removal · tb_voxel_grid_downsample
*Provenance: ops.py — 2D 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.