按建议,继续完成后续工作
结论:tool_semantics 的 T/M6/G43/G49 canonical 子集已通过 rs274 -t -i 纳入 upstream side-by-side baseline,M61 host-state 行为继续由 standalone fixture 验证,完整 native probes 验证通过。
This commit is contained in:
@@ -124,20 +124,22 @@ The current fixture expectations validate standalone behavior against both the
|
||||
vendored LinuxCNC source path and an upstream `rs274` side-by-side baseline for
|
||||
parser/conversion, arc geometry, offsets, feed-control, comment/logging,
|
||||
numbered-parameter, probing, spindle-orient, file-open reset, file-finish,
|
||||
tool-reload, canned-cycle, state-tag motion, tool-table setup, and O-word
|
||||
subroutine fixtures, plus threading/rigid tap, NURBS dispatch boundaries, and
|
||||
the comparable canonical runtime edge and program-end cleanup calls. Fixtures
|
||||
that depend on standalone-only runtime adapters, HAL/INI/tool-change state,
|
||||
upstream `rs274` output gaps such as `WAIT` or hidden NURBS control-point
|
||||
detail, or richer machine session state still need dedicated native LinuxCNC
|
||||
baselines.
|
||||
tool-reload, tool select/change/length-offset, canned-cycle, state-tag motion,
|
||||
tool-table setup, and O-word subroutine fixtures, plus threading/rigid tap,
|
||||
NURBS dispatch boundaries, and the comparable canonical runtime edge and
|
||||
program-end cleanup calls. Fixtures that depend on standalone-only runtime
|
||||
adapters, HAL/INI/tool-change state, upstream `rs274` output gaps such as
|
||||
`WAIT` or hidden NURBS control-point detail, or richer machine session state
|
||||
still need dedicated native LinuxCNC baselines.
|
||||
|
||||
Remaining positive fixtures that are not in the upstream `rs274` side-by-side
|
||||
baseline are intentionally held out until they get a dedicated native LinuxCNC
|
||||
baseline: `namedparam_semantics` depends on standalone INI/HAL adapter
|
||||
resolution, and `tool_semantics` depends on tool-change host state.
|
||||
`state_tag_motion` now compares its motion events with upstream `rs274`, while
|
||||
`UPDATE_TAG` events remain a standalone state-tag capture boundary.
|
||||
resolution. `state_tag_motion` now compares its motion events with upstream
|
||||
`rs274`, while `UPDATE_TAG` events remain a standalone state-tag capture
|
||||
boundary. `tool_semantics` now compares T/M6/G43/G49 canonical events with
|
||||
upstream `rs274`; M61 current-pocket host-state behavior remains covered by the
|
||||
standalone fixture expectation.
|
||||
|
||||
The kinematics probes currently cover LinuxCNC identity/trivial kinematics, the
|
||||
switchable `5axiskins` XYZBCW bridge-mill model, TRT `xyzac`/`xyzbc`
|
||||
|
||||
Reference in New Issue
Block a user