tb_points_zyx_to_keypoints_uv — 2D `typed` op

• Data kinds: points → keypoints

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

*No figure: this op takes points as input. A Studio program starting from an image cannot reach that type — see the runnable examples below for how it is used.*

Usage

Point cloud `(N,3) = (z, y, x) -> image coordinates (N,2) = (u, v)`.

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

:func:keypoints_uv_to_points の逆向き。不可逆 —— z が落ちる。

落ちる量は測れる: 往復して戻ってこない値は z 列そのもので、

`selftest` は「z の RMS = 落とした情報量」として数字で出す。

Args:

points: (N, 3) の (z, y, x)。

Returns:

(N, 2) float64 の (u, v) = (x, y)。

Raises:

ValueError: 形状不正 / 非有限。

2-D 進化レジストリへ橋渡しした reprconv の op `points_zyx_to_keypoints_uv。実装は同じで、呼び出し規約だけ 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.

Runnable examples (verified samples that actually call this op)

• (none yet)

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

identity · tb_keypoints_uv_to_points · tb_keypoints_to_image2d

Same category (`typed`)

tb_points_to_voxel · tb_estimate_point_normals · tb_iss_keypoints · tb_angle_3points · tb_project_points · tb_render_point_depth · 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).*

tb_points_zyx_to_keypoints_uv — 2D typed op