tb_keypoints_uv_to_points — 2D `typed` op

• Data kinds: keypoints → points

• Call: fullseye.apply(img, "tb_keypoints_uv_to_points", a=0.5, b=0.5) (the 2-D model is one image plus two scalar knobs a,b∈[0,1])

tb_keypoints_uv_to_points: input → output

*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_uv_to_points: stages (docs site)

On other images (synthetic scene / photo / coins. Top row: inputs, bottom row: their outputs. Knobs at default):

▸ tb_keypoints_uv_to_points: other inputs (docs site)

Usage

Image coordinates `(N,2) = (u, v) -> point cloud (N,3) = (z, y, x). An exit of keypoints`.

> The detailed description below is the original text — the summary and the headings are translated.

op 名に軸の約束が書いてあるのは、この repo で `keypoints` を産む

`match3d.project_points が **(u, v) = (列, 行)** を返し、points` を産む

`fuse3d.to_points(voxel)` が (z, y, x) を返すから —— 素直に「先頭 2 列」

として繋ぐと例外も NaN も出ないまま行と列が入れ替わる。ここでは

`y = v、x = u` と明示的に入れ替えて渡す。

:func:points_zyx_to_keypoints_uv と往復して bit 一致(z を渡した向き)。

Args:

keypoints: (N, 2) の (u, v)。

z: 載せる平面の z(スカラ、または (N,) の配列)。

Returns:

(N, 3) float64 の (z, y, x)。

Raises:

ValueError: 形状不正 / 非有限 / z の長さ不一致。

2-D 進化レジストリへ橋渡しした reprconv の op `keypoints_uv_to_points。実装は同じで、呼び出し規約だけ op(v, a, b) に合わせてある。この op に調整点は無く、a も b` も使われない。

References (sample data, literature)

• 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.

Try it in Studio

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_uv_to_points 0.50 0.50

▸ Load this pipeline · Load & run

Runnable examples (verified samples that actually call this op)

The examples below call the underlying ledger op keypoints_uv_to_points. 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).

• representation_roundtrip — py -3.11 examples/representation_roundtrip.py

Ops the type connects to (they accept `points` as input)

identity · 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

Same category (`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).*

tb_keypoints_uv_to_points — 2D typed op