-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange bug for elliptic curves over number fields #7930
Comments
comment:1
More precisely it produces
|
comment:2
In the middle of Tate's algorithm it needs to know how many roots a cubic mod P has, where P is the prime, and in doing this it constructs the polynomial ring over the residue field on the fly. These poly rings are constructed in such a way that for each field the rings is only constructed once (I think). the errors a re something which goes wrong in that construction. I am CC'ing robertwb who I hope will be able to help! |
comment:3
No time to look t it now, but I've added this to my bug hit list for this upcoming week. |
comment:4
Note that in #7935 we have added a #random to line 1026 in ell_number_field.py, because the output of the minimal_global_model produced two differnt answers. Maybe this is linked to this bug and the #random can be removed once the issue here is fixed. This is very strange. For that curve E2, I sometimes get
but sometimes I get
|
comment:5
Note that E has bad reductions at 3 and 11, which are both inert in both those cubic fields. That means that when we are finding the local data for each field, we construct the residue fields which are of order This might help debugging the session will have more than one field of the same order, with different defining polynomials. |
comment:6
Any news on this ? |
comment:7
This problem seems to have gone away now -- in 4.4.4 the above script works fine. Can we close the ticket? |
Author: Chris Wuthrich |
comment:8
Almost. Here is a patch that adds the example as a doctest (in a _function so as not to appear in the documentation) to make sure that the bug does not appear again in the future. |
exported against 4.4.4.alpha0 |
comment:10
Attachment: trac_7930.patch.gz Looks good & tests fine on 4.4.4.alpha0. |
Reviewer: John Cremona |
Merged: sage-4.5.2.alpha0 |
The following code
produces a
TypeError
. Having played around with this for hours, I believe that all lines in the above code are necessary to produce the bug. Especially both the torsion and local data computations over another field. I have no idea whatsoever of where to look for the error.CC: @JohnCremona @williamstein @robertwb
Component: elliptic curves
Author: Chris Wuthrich
Reviewer: John Cremona
Merged: sage-4.5.2.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/7930
The text was updated successfully, but these errors were encountered: