-
-
Notifications
You must be signed in to change notification settings - Fork 568
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
problem in evaluation dual isogeny #10888
Comments
comment:1
The problem is very simply that evaluation in a polynomial with two variables does not give back a constant, but a constant polynomial. Is this a bug ?
It is certainly not consitent with this :
|
comment:2
I came across something very similar indeed before and thought I had fixed it. I should check to see if the patch I made ever got merged. |
comment:3
Replying to @JohnCremona:
See #8502. |
comment:4
John, thanks to your link I found quickly what is the problem. Consider
The first returns an element in the base ring, while the others are still polynomials. This is correct with respect to the documentation apart from the middle one. So something has to be changed there. I am uncertain what. I attach a patch that changes I will aks this to sage-devel. |
only uploaded for discussion |
Attachment: trac_10888_evaluation_of_multi_polynomials.patch.gz Attachment: trac_10888.patch.gz exported against 4.6.2. Only this patch should be applied. |
Author: wuthrich |
comment:5
From the discussion on sage-devel, I learned that I should not change the functioning of evaluation in this ticket. To solve the bug in the isogenies, I simply make the evaluations in the code to be evaluations without keywords. Then it is no longer ambiguous. I will open another ticket about the issue with evaluation and substitution. |
comment:6
The other, more general issue is now #10946. |
comment:7
The patch works and I'm willing to give a positive review, but the doctest takes 2.6 cpu secs on my laptop (64-bit Intel Core2 U9400 @ 1.40GHz... not the fastest cpu ever, but still decent), it would make sense to tag this test as long. Alternatively, though I don't know if this is acceptable for Sage standards, the doctest could be slightly changed. The code below fails in 4.6.2 and is fixed by this patch; it takes only 0.2 secs, because it uses Kohel's algorithm (instead of Vélu's formulae) to compute
Finally, the doctest does not show up in the reference manual, because it is in the docstring of the method |
comment:8
I have also tested the patch and agree that it works (applied to 4.7.alpha5, all tests in elliptic curves pass). I don't think that the test is too long. This whole file is quite long as a whole (nearly 30s) but several other tests are longer! I expect to be splitting this file into two before long, so I am happy to leave off the "long time" tag. I would also be happy to have defeo's additional code added. It doesn't matter that this example does not appear in the reference manual. It stays in as a test, to make sure this will continue to work in future; but it does not add a lot to for the user, I think. If you want it to appear in the manual, insert it in the header section of the file (instead, or as well). I'll set this to "positive review" now; if you (defeo) wants to make further changes to the tests put it back to "needs review" and I'll look at it again. |
Reviewer: Luca De Feo, John Cremona |
Changed author from wuthrich to Chris Wuthrich |
Merged: sage-4.7.1.alpha0 |
The following bug was reported by J. Gillibert.
This gives back a
Component: elliptic curves
Keywords: isogenies
Author: Chris Wuthrich
Reviewer: Luca De Feo, John Cremona
Merged: sage-4.7.1.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/10888
The text was updated successfully, but these errors were encountered: