measure_backend asked SMLib for mass properties at 1e-8, the finest its
integrator allows and below the range SmApiBrepComputeMassProperties
documents ("Relative accuracy, clamped to [1e-4, 1e-1]", SmApiQueries.h,
whose cost is "governed by dRelativeAccuracy"). The tight request was there
because the documented range did not hold on faces bounded by circles
(KNOWN_ISSUES.md); the fork's dcbb07d integrates each trim-curve knot span
on its own, and such faces now meet it (a cylinder's volume 1.8e-6 off at
1e-4). At 1e-8 SMLib's measure was most of the regression rig's time on a
modelled thread (threads/602).
The measure now asks 1e-4: ten times inside the 1e-3 it is held to (AGREE
against the mesh measure, and the rig's volume and area tolerance). NURBS
spheres and tori can still miss 1e-4 by a small factor (tangency-labs/
solidcore#384; a torus's volume 2.5e-4 at 1e-4), inside that 1e-3.
Brep::mass_properties keeps MEASURE_ACCURACY (1e-8) as its tests' default.
SMLIB_REV: the fork at dcbb07d.
Not built: base in progress (kernel-smlib/no-truck 52f25ca3 does not build).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017itGh5fpMEousnZ91cYcVt