按建议继续完成后续工作
结论:upstream rs274 side-by-side 基线已扩展到 NURBS G5/G6 调度边界;控制点细节仍由 standalone fixture 覆盖,完整 native 验证已通过。
This commit is contained in:
@@ -111,10 +111,11 @@ 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, offsets, feed-control, comment/logging, numbered-parameter,
|
||||
spindle-orient, file-open reset, file-finish, tool-reload, and O-word
|
||||
subroutine fixtures, plus threading/rigid tap and the comparable canonical
|
||||
runtime edge calls. Fixtures that depend on standalone-only runtime adapters,
|
||||
HAL/INI/tool table setup, upstream `rs274` output gaps such as `WAIT`, or
|
||||
richer machine session state still need dedicated native LinuxCNC baselines.
|
||||
subroutine fixtures, plus threading/rigid tap, NURBS dispatch boundaries, and
|
||||
the comparable canonical runtime edge calls. Fixtures that depend on
|
||||
standalone-only runtime adapters, HAL/INI/tool table setup, upstream `rs274`
|
||||
output gaps such as `WAIT` or hidden NURBS control-point detail, or richer
|
||||
machine session state still need dedicated native LinuxCNC baselines.
|
||||
|
||||
The kinematics probes currently cover LinuxCNC identity/trivial kinematics,
|
||||
the switchable `5axiskins` XYZBCW bridge-mill model, and the TRT `xyzac`/`xyzbc`
|
||||
|
||||
@@ -69,9 +69,10 @@ semantic rewrites:
|
||||
path. The upstream `rs274` side-by-side baseline now covers simple motion,
|
||||
offsets, feed-control, comment/logging, numbered-parameter, spindle-orient,
|
||||
file-open reset, file-finish, tool-reload, and O-word subroutine fixtures;
|
||||
it also covers threading/rigid tap and comparable canonical runtime edge
|
||||
calls. Adapter-heavy fixtures and upstream `rs274` output gaps such as
|
||||
`WAIT` still need dedicated native LinuxCNC baselines.
|
||||
it also covers threading/rigid tap, NURBS dispatch boundaries, and comparable
|
||||
canonical runtime edge calls. Adapter-heavy fixtures and upstream `rs274`
|
||||
output gaps such as `WAIT` or hidden NURBS control-point detail still need
|
||||
dedicated native LinuxCNC baselines.
|
||||
|
||||
## Current Drift Conclusion
|
||||
|
||||
|
||||
@@ -507,10 +507,11 @@ Current verified progress:
|
||||
native LinuxCNC canonical output for simple motion, offsets, feed-control,
|
||||
comment/logging, numbered-parameter, spindle-orient, file-finish, and
|
||||
tool-reload fixtures. It now also includes file-open reset and O-word
|
||||
subroutine fixture coverage, threading/rigid tap coverage, plus comparable
|
||||
canonical runtime edge calls. Native output is filtered to the event classes
|
||||
each standalone fixture explicitly expects, while upstream `rs274` output
|
||||
gaps such as `WAIT` remain covered by the standalone harness rather than
|
||||
subroutine fixture coverage, threading/rigid tap coverage, NURBS dispatch
|
||||
boundary coverage, plus comparable canonical runtime edge calls. Native
|
||||
output is filtered to the event classes each standalone fixture explicitly
|
||||
expects, while upstream `rs274` output gaps such as `WAIT` and hidden NURBS
|
||||
control-point detail remain covered by the standalone harness rather than
|
||||
being treated as side-by-side evidence. The comparison does not introduce a
|
||||
project-authored CNC semantics oracle.
|
||||
- `tests/fixtures/gcode_errors/g1_zero_feed.ngc` and
|
||||
|
||||
Reference in New Issue
Block a user