fullseye

v13 — production hardening, cross-project packaging, perception stack

Goal (user): take the image-processing engine to (1) a practical level usable across other projects, (2) a completeness where future research lacks nothing, and (3) usable as the agent’s own skill. Everything below is local; nothing is pushed (human-gated). Full suite at each step stayed green.

Correctness

The six deferred correctness bugs are fixed, each ground-truth verified with a regression test (see tests/test_fix_*, test_ncc_normalization, test_region_geom_binary):

Cross-project use (leg 1)

Perception stack (robotics / physical-AI)

All numpy-native, ground-truth tested, exposed under fullseye:

module capability
stereo dense disparity (block matching) → depth → point cloud
terrain point cloud → 2.5-D elevation map → traversability + foothold score
detect segment objects → shape/moment descriptors → nearest-prototype identify
registration Kabsch (corresponded) + ICP (unmatched) → object 6-DoF pose
pose silhouette skeleton graph + principal axis → posture descriptor
imgio coercion, colormaps, overlays, image/PLY export (no matplotlib)

End-to-end verified: stereo → depth → point cloud → elevation → traversability.

Fullseye Studio

py -3.11 studio.py (or fullseye-studio): an HDevelop-style visual workbench — searchable operator browser, build/reorder a pipeline, tune each stage’s a,b knobs, watch the intermediate result live, export to a --ops string or Python. The PipelineModel logic is headless and unit-tested; the PySide6 view is smoke-tested offscreen.

Research completeness (leg 2)

Disclosure policy

Public-facing text (README, package metadata) presents Fullseye as an in-house library reimplemented from published algorithms and open-source software; it does not name any proprietary product. Common filter names and OSS function names are fine. Coverage/benchmark numbers are measured, not asserted.