typed op• Data kinds: keypoints → keypoints
• Call: fullseye.apply(img, "tb_keypoints_rowcol_to_uv", a=0.5, b=0.5) (the 2-D model is one image plus two scalar knobs a,b∈[0,1])
• GPU: none (CPU reference implementation only)
*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).*
*Knob b does not change the output (measured: identical at 0.1 / 0.5 / 0.9).*
Stages (the ops that come before → this op, left to right):
▸ tb_keypoints_rowcol_to_uv: stages (docs site)
On other images (synthetic scene / photo / coins. Top row: inputs, bottom row: their outputs. Knobs at default):
▸ tb_keypoints_rowcol_to_uv: other inputs (docs site)
Image points (row, col) → (u, v) = (col, row). The bridge between the two conventions of the keypoints sort.
> The detailed description below is the original text — the summary and the headings are translated.
keypoints 型には 2 つの軸の約束が同居している(実測): calib.project_3d_point などは (row, col)、project_points / dlt_pose / pnp_ransac は (u, v) = (列, 行)。取り違えても例外は出ず、姿勢が鏡に映ったように出る(W2 の実測: t = (−0.565, 0.61, 3.21) のはずが (0.1, −0.05, 3.0))。列を入れ替えるだけだが、どちらの向きかを op 名に書くため
逆向きの keypoints_uv_to_rowcol と 2 本に分けてある(中身は同じ入れ替え)。
Args:
keypoints: (N, 2) の (row, col)。
Returns:
(N, 2) float64 の (u, v)。
Raises:
ValueError: (N, 2) でない / 非有限 / 空。
2-D 進化レジストリへ橋渡しした reprconv の op keypoints_rowcol_to_uv。実装は同じで、呼び出し規約だけ op(v, a, b) に合わせてある。この op に調整点は無く、a も b も使われない。
• 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_keypoints 0.50 0.50 tb_keypoints_rowcol_to_uv 0.50 0.50
▸ Load this pipeline · Load & run
The examples below call the underlying ledger op keypoints_rowcol_to_uv. 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).
• type_connectivity_tour — py -3.11 examples/type_connectivity_tour.py
keypoints as input)identity · tb_keypoints_uv_to_points · tb_keypoints_to_image2d · tb_keypoints_uv_to_rowcol
typed)tb_points_to_voxel · tb_estimate_point_normals · tb_iss_keypoints · tb_project_points · tb_render_point_depth · tb_points_render · tb_statistical_outlier_removal · tb_radius_outlier_removal
*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.