jyviko b71e5ae6f4 Tests: edges are read on their NURBS forms, a chamfer's chain is its caller's, the cap test's hatch ...

- An SMLib circle edge's `interval` is on its NURBS form (`Edge::parameters`), and an analytic
  face's `domain` on the form's (u, v). edges_are_on_smlibs_curves evaluated `curve` at the
  form's interval and took the domain for angles; it checks the side's whole turn and height
  on the form and a rim's turn by `curve_interval`. The tangent hole test's edge middles were
  read the same way (the copy seemed to join faces on opposite sides of the line).
- kernel::chamfer blends the edges it is given; a feature's pick is extended by
  kernel::tangent_chain first (doc eval). The chamfer tests do the same:
  one_chamfer_pick_follows_the_tangent_chain_at_any_part_size removes its 54.66 mm³ again.
- Since the section hatch per part (#8529) a cut is tinted with the hatch colour its body's
  name picks (Body1: steel); the GPU cap test turns the part hatch off, as the CPU one does
  (2885f101b on devgreen-engine-builds).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-29 12:20:38 -04:00

..

src

GPU tessellation: the shader's basis slots follow the CPU evaluator's highest degree

2026-10-28 22:11:39 -04:00

tests

Tests: edges are read on their NURBS forms, a chamfer's chain is its caller's, the cap test's hatch

2026-10-29 12:20:38 -04:00

Cargo.toml

GPU tests build their designs with SMLib, and the GPU jobs fetch it

2026-10-28 22:12:31 -04:00