Open AndrewVSutherland opened 2 years ago
See also #4933 for some suggestions on changing how downloads of search results work.
I just tried out the Sage version of this and have two suggestions:
for lab, E in zip(labels, curves): E._lmfdb_label = lab
Then, for any curve E in the list created, the user can see its label easily, and can even run E.lmfdb_page() to see its LMFDB home page.I suspect that people using this will ask for more of the data stored for the curve in the LMFDB to be included in the file (rank, generators, etc), which could be done in a follow-up. Again, these extra properties can be stored in the Sage elliptic curve object.
I will try the Magma and gp version next.
Magma and gp version work fine -- but again I suggest having the hint about make_data display when the file is read. In the case of gp I would suggest "curves = make_data();" with a semicolon, as otherwise the user sees the list (which ir not pretty).
I'll be happy to review a version with these minor changes.
I would not print anything, instead, I would move the To create
higher up, e.g.:
# Elliptic curves downloaded from the LMFDB on 23 January 2022.
# Query "{'conductor': 11}" returned 3 curves.
#
# To create a list of curves, type "curves = make_data()"
#
#
# Below are two lists, one called labels, and one called data (in matching order).
# Each entry in the data list has the form:
# [[a1, a2, a3, a4, a6] Weierstrass coefficients]
# defining the elliptic curve y^2 + a1xy + a3y = x^3 + a2x^2 + a4x + a6.
It would be nice if the search result downloads for elliptic curves included a corresponding list of labels and a make_data function that would create the elliptic curves, as is done for the genus 2 curve search result downloads.