cut_force_csv_load — DRIVE `cutting` op

• Data kinds: any × any → table

• Call: import fullseye as fs; fs.ledger.cut_force_csv_load(path, license: 'str') -> 'dict' (to call the implementation directly, import cutting; cutting.cut_force_csv_load(path, license: 'str') -> 'dict'; from the registry, opsdrive.get("cut_force_csv_load"))

Usage

Reads the CSV of blade forces written by a finite element cutting simulation (line 1 is Rcforc, line 2 the column names, columns alternate between time and the 3 force components).

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

想定しているのは arXiv:2105.12244 が公開したデータセット(CC BY-NC 4.0 = 非商用)。license は呼び手が必ず書く(データの使い道を返り値に残すため、空なら ValueError)。データは repo に入れず、置き場所は環境変数で渡す。

返り値: t_s、F_xyz(N、(N, 3))、license、path は返さない(ローカルパスを記録に残さない)。

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 `table` as input)

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

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).*

cut_force_csv_load — DRIVE cutting op