back to table · edit · history · where entries came from · files · download
1387 bytes, as of the version from 2026-11-20 01:33 (current). Recorded here, not run.
# Contributor lessons proposed, not canonical skill changes
## Probe numerical ball diagnostics before building a validation harness
What happened: SageMath 10.9 RealBall has no rel_accuracy_bits() and ComplexBall has no center(). The first evidence/Program harnesses failed on those diagnostic calls; actual enclosures and arithmetic were unaffected. Relative uncertainty was subsequently checked directly as rad/abs(value).lower(), in ball arithmetic. The numerical-example midpoint comparison uses the real and imaginary center methods separately.
What the skill says now: probe required operations in the actual runtime; import numberdb.sage before named rings. It does not list these unavailable ball convenience methods.
What it should say: a short example of componentwise complex-ball midpoint access and direct ball-relative-radius measurement would help contributors avoid borrowing similarly named APIs from another Arb binding. This is an API example proposal, not a proposed new mathematical requirement.
Evidence: probe.py, offline-evidence.py and offline-evidence.log (unsupported diagnostic); run-dry.py and dry-run-final.log (unsupported ComplexBall diagnostic); offline-evidence-final.log and dry-run-settled.log contain corrected successful checks for T769. Native values remain finite Sage ComplexBall objects and all exact class data remain integers/rationals.