typed op• Data kinds: points → signal
• Call: fullseye.apply(img, "tb_env_lightbox", 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.*
Sweeping knob a (0.1 / 0.5 / 0.9, the other knob at its default):
▸ tb_env_lightbox: knob a sweep (docs site)
Sweeping knob b (0.1 / 0.5 / 0.9, the other knob at its default):
▸ tb_env_lightbox: knob b sweep (docs site)
Stages (the ops that come before → this op, left to right):
▸ tb_env_lightbox: stages (docs site)
On other images (synthetic scene / photo / coins. Top row: inputs, bottom row: their outputs. Knobs at default):
▸ tb_env_lightbox: other inputs (docs site)
Environment of a photo light box (broad overhead light + a faintly bright surround). Achromatic.
Whereas env_studio is a dark room + 2 small softboxes "for dramatic looks", this one is an environment in which a machined surface looks like a machined surface. It is built to satisfy 2 conditions found in the measurements of 2026-09-05:
• The surroundings must be bright ―― in a dark environment aluminium turns pitch black (a metal with reflectance ~0.9 appears black because what it reflects is black).
• Even so, there must be a gradient ―― in a perfectly uniform environment every anisotropic lobe returns the same value, so the machining marks disappear. Brush marks are visible because the marks stretch the light and dark of the environment along the mark direction.
Machining marks only show when viewed at an angle (a plane viewed from straight above concentrates the reflection direction of every pixel at the zenith and does not sweep the environment gradient). Around optical_camera(tilt_deg=50〜70) is a guide.
The optics op env_lightbox 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 base (default 0.45) and b sweeps key (default 4).
• 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_lightbox 0.50 0.50
▸ Load this pipeline · Load & run
The examples below call the underlying ledger op env_lightbox. 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.