marker_track — DRIVE `tacslip` op

• Data kinds: image2d × image2d × scalar × scalar × scalar → table

• Call: import fullseye as fs; fs.ledger.marker_track(m_ref, m_cur, dark: 'float', pitch_px: 'float', r_px: 'float', piv: 'bool' = False) -> 'dict' (to call the implementation directly, import tacslip; tacslip.marker_track(m_ref, m_cur, dark: 'float', pitch_px: 'float', r_px: 'float', piv: 'bool' = False) -> 'dict'; from the registry, opsdrive.get("marker_track"))

Usage

> This operator's description has not been translated yet. The original text follows as it is.

基準・荷重後のマーカー像(:func:marker_image)から変位ベクトル場: 検出(:func:marker_detect、2 枚)→ 連続性で対応

(:func:marker_match_grow)→ `u = p1 − p0 [px]。返り p0・p1・u(各 (M, 2))、matched、n0・n1`。

`piv=True なら :func:pivops.piv_cross_correlate の場(第 2 実装、探索 ±0.12 窓)を piv_flow・piv_info・piv_at`(点列で標本化する

関数)として付ける。Raises ValueError: 2 枚の形が違う。

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.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Runnable examples (verified samples that actually call this op)

• poc_tacsim_marker_shear — py -3.11 examples/poc_tacsim_marker_shear.py

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

course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same

Same category (`tacslip`)

mindlin_partial_slip · mindlin_traction · hertz_surface_ur · hertzian_tangential_inner · cerruti_kernel · cerruti_surface_displacement · membrane_shear_field · membrane_markers

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

marker_track — DRIVE tacslip op