#15299: Incorrect results for analytic Sha due to low precision
-----------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-5.13
Component: elliptic curves | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------------+-------------------------
Description changed by jdemeyer:
Old description:
> See [https://groups.google.com/forum/#!topic/sage-support/rYQ4rWyncG4]
New description:
See [https://groups.google.com/forum/#!topic/sage-support/rYQ4rWyncG4]
{{{
sage: E=EllipticCurve(QQ,[0, 0, 1, -79, 342]);
E.sha().an(),E.sha().an_numerical()
(0, 1.00000000000000)
sage: E.lseries().deriv_at1(100*sqrt(E.conductor()) + 10) # L1,
error_bound
}}}
This seems to be due to inappropriate use of Python floats instead of more
precise objects.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/15299#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
