#10665: bug in elliptic curve two_descent command
-----------------------------------+------------------------
Reporter: was | Owner: cremona
Type: defect | Status: new
Priority: minor | Milestone: sage-6.3
Component: elliptic curves | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------------+------------------------
Comment (by pbruin):
The cause is that each time you call `mwrank_EllipticCurve.two_descent()`,
it creates a new `__descent` (the 2-descent data) but does not reset the
`__saturate` bound. Therefore no saturation is done on the new
`__descent` data, which is bad because `getbasis()` depends on the
saturation having been done. I'm now testing a patch.
--
Ticket URL: <http://trac.sagemath.org/ticket/10665#comment:7>
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/d/optout.
