Closed JohnCremona closed 7 years ago
1 and 2 are both done. Let me know if you are happy with nfcurves so I can delete the old versions.
Thanks -- it may not be until tomorrow (likewise your other PR -- I was not expecting it so fast!)
OK -- looks good, you can delete the nfcurves*old collections (or I will if you are too busy celebrating!)
Done (celebrating will commence shortly :))
Same again please (both bmfs and nfcurves, same collections as before). This adds data over 2.0.3.1 for range 120k-130k (both bmfs and nfcurves); adds some missing cm curves; and adds galrep data to all the nfcurves.
Done. Let me know once you have checked the results and I will delete the old versions.
Looks good, the old ones can go. e.g. see the large exceptional prime at EllipticCurve/2.0.3.1/109561.1/CMa/1. Thanks!
Same again would add data for field 2.0.3.1 range 130k-140k for both Bianchi forms and elliptic curves. In a week or so there will be more so it's fine to ignore this -- not bug fixes, just more date.
Done!
Thanks a lot
On 2017-08-03 I updated bmfs.{forms,dimensions} and elliptic_curves.nfcurves myself.
Just adding this to keep the record up-to-date -- possibly not neccessary?
@JohnCremona I think this is useful. When I get a chance I will modify the update script to log information in a mongo db collection, but I have not done this yet.
Please could we copy the following to the cloud?
It may be that we do not yet need to copy bmfs to the cloud since the code which refers to it is all beta but I think it would be safer to do so now: after the next push master -> prod anyone looking at an elliptic curve over an imaginary quadratic field will see a link to a Bianchi modular form but that will surely not work if the data is not there. (I should perhaps make those links not appear except in beta mode -- let me know if that is the case!)