Bill Allombert on Mon, 11 Dec 2023 13:03:32 +0100 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: getting strange ellheight() error for number field point and curve |
On Mon, Dec 11, 2023 at 10:22:47AM +0000, John Cremona wrote: > You can help yourself at https://www.lmfdb.org/EllipticCurve/. Note that > if you go to the home page of any curve, for example (random!) > https://www.lmfdb.org/EllipticCurve/2.2.76.1/144.1/d/1, on the right-hand > side you can see a link "Download all code to PariGP" which then shows you > something like > https://www.lmfdb.org/EllipticCurve/2.2.76.1/144.1/d/1/download/gp which > gives you the code to create that curve in gp and compute some of the > quantities there. I think that with recent (and perhaps not so recent) > advances in pari, there are more pieces of code which we could include. Indeed, this is exactly what I did! However the LMFDB does not list points for all curves of positive rank, and all the curves in the LMFDB are given by nice models that does not trigger this bug. What I did was to apply some random [u,r,s,t] transformation, but my choice was not random enough. Are there curves in the LMFDB which do not admit a minimal model ? How to get them ? > By the way, as ellbsd() was mentioned, I have a couple of comments: first > that you cannot rely on having a global minimal model, as they do not > always exist, so rather than having functions which give an incorrect > answer when a model is not globally minimal, it is better (where possible) > to adjust by the "difference" between the given model and a minimal model > (which do of course exist locally). Indeed, that is what PARI was attempting to do, except it assumed the model was integral. Cheers, Bill