#10952: better numerical accuracy testing
-----------------------------------------------------------------------+----
Reporter: robertwb |
Owner: mvngu
Type: enhancement |
Status: needs_work
Priority: critical |
Milestone: sage-4.7.2
Component: doctest |
Keywords: sd32
Work_issues: |
Upstream: N/A
Reviewer: Jason Grout, Mariah Lenox, William Stein, John Palmieri |
Author: Robert Bradshaw, Rob Beezer
Merged: |
Dependencies:
-----------------------------------------------------------------------+----
Comment(by leif):
Replying to [comment:30 jhpalmieri]:
> I think the regexp should something like
{{{
' ((\.[0-9]+|[0-9]+(\.[0-9]*)?)e[+-]?[0-9]+)'`
}}}
But that doesn't match `1ee7` :(
You can of course match funny things first, i.e. use more general
patterns, but you then have to check the matched expression further before
passing it to `float()`.
The whole idea isn't that bad, but carries the danger that people simply
increase the tolerance (too much) just to make doctests pass ''somehow'',
without caring where the variations originate from.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10952#comment:31>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
