#8828: Lower height bound for elliptic curves
-------------------------------------+-------------------------------------
Reporter: robertwb | Owner: cremona
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: elliptic curves | Resolution:
Keywords: | Merged in:
Authors: Robert Bradshaw, | Reviewers:
John Cremona | Work issues:
Report Upstream: N/A | Commit:
Branch: | 361590b875996d1a5eadd350e110052341603ca8
u/cremona/ticket/8828 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
I'm now reading the code and documentation. Apart from a number of small
spelling/typographical things (for which I'll just make a reviewer patch),
there are a few functions of which the documentation is missing:
- `EllipticCurve_number_field.height_function()`
- the functions `frame_data()` and `unframe_data()` in
`period_lattice_region.pyx`
By the way, I don't think my paper of last year makes any of this
redundant. My method is almost certainly slower (I don't know by how
much; it is only implemented as a PARI script and I did not make a lot of
effort to make it fast, but I doubt it can beat the algorithms in this
patch). Which method is most suitable probably depends a lot on the
curve.
--
Ticket URL: <http://trac.sagemath.org/ticket/8828#comment:32>
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.
