rmse_correspondence — 3D `metrics` op

• Data kinds: points × points → measurement

• Call: import metrics3d; metrics3d.rmse_correspondence(a, b) (or ops3d.get("rmse_correspondence"))

Usage

RMSE over known correspondences (same index) = sqrt(mean |a_i − b_i|²). → scalar. For judging the registration residual.

Background guides (the physics and conventions behind this op)

• blender_interop — Blender との併用 — 形を作って fullseye で測る(軸・単位・正解データの罠)

• measurement_uncertainty — 計測の不確かさと校正の知識 — 「測れている」を主張するために

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)

• metrics_eval — py -3.11 examples_3d/metrics_eval.py

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

vol_gaussian_psf · fuse_to_voxel · fresnel_reflectance · snell_angle

Same category (`metrics`)

chamfer_distance · hausdorff_distance · fscore · normal_consistency · voxel_iou · pose_error

*Provenance: metrics3d.py — 3D operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

rmse_correspondence — 3D metrics op