mesh_detail_map — 3D `resolution` op

• Data kinds: mesh → table

• Call: import fullseye as fs; fs.ledger.mesh_detail_map(V, F) (to call the implementation directly, import meshres; meshres.mesh_detail_map(V, F); from the registry, ops3d.get("mesh_detail_map"))

Usage

Per-vertex coarseness and detail of a mesh (`table`).

`coarseness` (nv,) — mean incident edge length, mapped linearly from the

5th percentile (0) to the 95th (1) and clipped; `edge_length` (nv,) the

raw value. `detail` (nv,) — mean angle (radians) between the normals of

the faces around the vertex divided by the mean incident edge length: a

curvature proxy in 1/unit that is high where the *data* already carries

relief, independent of how densely it is sampled. `relief_weight` (nv,)

= `coarseness × (1 − detail_norm)` — 1 where the mesh is coarse and

smooth (add synthetic detail), 0 where it is fine or already rough — the

weight :func:render3d.mesh_displace_fbm-style steps should multiply

their amplitude by. Also `stats` for each map.

Background guides (the physics and conventions behind this op)

• depth_sensors — 深度センサの知識 — 測距原理・実機の値・欠測の出方

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)

• mesh_resolution_demo — py -3.11 examples_3d/mesh_resolution_demo.py

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

fuse_to_voxel · mesh_select_lod

Same category (`resolution`)

mesh_edge_stats · mesh_split_long_edges · mesh_isotropic_remesh · mesh_sample_points · mesh_lod_chain · mesh_select_lod · mesh_reduction_report · mesh_decimate_preserving

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

mesh_detail_map — 3D resolution op