Opened 7 years ago

Last modified 6 years ago

#18968 new enhancement

LMFDB label for elliptic curves

Reported by: David Roe Owned by:
Priority: minor Milestone: sage-6.9
Component: elliptic curves Keywords:
Cc: Jennifer Balakrishnan, Alyson Deines Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

We should support LMFDB labels, e.g.

sage: EllipticCurve('11.a2') == EllipticCurve('11a1')
True

See http://www.lmfdb.org/knowledge/show/ec.q.lmfdb_label for details on LMFDB labels.

Change History (10)

comment:1 Changed 7 years ago by John Cremona

The best way to do this would be to change the SQL database (small version standard, extended version optional) to include these labels. Then it will be easy. Otherwise conversion of labels is non-trivial (as you know very well, roed!).

The entire permutation is also available at https://github.com/JohnCremona/ecdata/tree/master/alllabels

comment:2 Changed 7 years ago by Kiran Kedlaya

It might also be nice to have a method that returns the URL in LMFDB for a given elliptic curve when possible (i.e., when the LMFDB label is known).

comment:3 Changed 7 years ago by John Cremona

Sure, though much grander plans are around (with no-one yet having the time to do it) for a good interface from Sage to LMFDB using the api Harald wrote (see http://www.lmfdb.org/api/).

Actually Kiran's proposal is much easier since the LMFDB does understand Cremona labels so the URL "http://www.lmfdb.org/EllipticCurve/%s" % E.label() should always work right now.

comment:4 Changed 6 years ago by Frédéric Chapoton

Branch: public/18968
Commit: d4781c3e1f9d7b519461d70fb4a1d7bf075608b5

Here is a poor-man tentative for adding links to lmfdb, not working.


New commits:

d4781c3trying to add links to lmfdb (not working)

comment:5 Changed 6 years ago by John Cremona

This is a great idea. Note that the LMFDB can parse URLs of the form .../EllipticCurve?/11a1 where the last part '11a1' is the Cremona label, as well as the LMFDB label version with a ".".

comment:6 Changed 6 years ago by Frédéric Chapoton

this:

http://www.lmfdb.org/EllipticCurve/11a1/

does not work (ie does not lead to the page of the curve itself)

So what is the correct syntax for the link ?

comment:7 Changed 6 years ago by git

Commit: d4781c3e1f9d7b519461d70fb4a1d7bf075608b520202426570dd3b613d0ab3c56bf5017337729db

Branch pushed to git repo; I updated commit sha1. New commits:

8d7831eMerge branch 'public/18968' in 7.4.b5
2020242trac 18968 link to lmfdb page with correct url

comment:8 Changed 6 years ago by Frédéric Chapoton

ok, it seems to work using

http://www.lmfdb.org/EllipticCurve/Q/11a1

Should I move the branch to another ticket, because this is not the exact aim of this one ?

comment:9 Changed 6 years ago by John Cremona

Sorry I got that wrong but you know what I meant to say. Yes, it is a different thing than the title of this ticket and so should be separate. We plan via ODK to have a much more systematic interface from Sage to LMFDB objects and this can be the start of that.

comment:10 Changed 6 years ago by Frédéric Chapoton

Branch: public/18968
Commit: 20202426570dd3b613d0ab3c56bf5017337729db

see now ticket #21533 for adding the webpage method

Note: See TracTickets for help on using tickets.