slice_push_from_track — DRIVE `cutting` op

• Data kinds: scalar × signal × signal → scalar

• Call: import fullseye as fs; fs.ledger.slice_push_from_track(theta_deg: 'float', x_mm, z_mm) -> 'float' (to call the implementation directly, import cutting; cutting.slice_push_from_track(theta_deg: 'float', x_mm, z_mm) -> 'float'; from the registry, opsdrive.get("slice_push_from_track"))

Usage

Computes ξ from the trajectory (x, z) of 1 point on the blade (from the image) and the cutting-edge inclination θ (from the image). The velocity is the direction of a line fit to the trajectory (ξ is a ratio).

Pass only the section where pushing occurs. Mixing in the entry phase (while the wrist is still compressing) makes the blade lag behind the command and biases ξ — use the steady section where the blade cuts the full width of the food (the PoC confirmed it returns 0.63 → 0.57 = the true value).

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_food_cutting_measure — py -3.11 examples/poc_food_cutting_measure.py

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

spin_from_marker_sequence · carla_transform_matrix · carla_pose_to_world · carla_camera_pose · carla_xy_yaw · carla_scene_load · town_chain · osm_parse

Same category (`cutting`)

cutting_scene · cutting_face_render · cutting_edge_render · cutting_episode_synth · cutting_wrist_mjcf · knife_edge_track · cut_depth_from_side · slice_thickness_profile

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

slice_push_from_track — DRIVE cutting op