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
Improve minimal_quadratic_twist() #14060
Comments
comment:2
Precision issue is #13163. |
This comment has been minimized.
This comment has been minimized.
comment:3
I see two possibilities here: either rename this function I am CC-ing Chris W since the only place where this function is used (according to Of course this is in addition to adding one line to return self of |
comment:4
In sha_tate and in general for p-adic L-functions we can only twist by quadratic characters (well, I can only, maybe someone else knows more). So if changing the function one has to be careful to twist only by quadratic twists for these two cm curves. But if I remember correctly, we currently exclude cm curve (which we would not have to do in fact). |
comment:5
Looking more carefully at the code (I am not embarrassed that I wrote it but could not remember) I see that for j=0 and j=1728 the curve returned is always a quadratic twist. So the "additionally" part of the ticket's current description is incorrect. If you agree with me on that (and a second opinion would be welcome!) then that just leaves the first part which I can easily implement by adding one line. |
comment:6
We could have a minimal_twist function, too, if you wish, but I need minimal_quadratic_twist for modular symbols. If you can simplify the current function that is certainly a good thing to do. I am not sure what changes you want to make, but if you do them, I should be able to look at them and review it quickly. (from Besancon) |
Branch: u/cremona/ticket/14060 |
This comment has been minimized.
This comment has been minimized.
Author: John Cremona |
Commit: |
comment:8
I have implemented the small improvement (do nothing if the conductor is square-free) with a new doctest, and also expanded on the documentation in the exceptional cases j=0, 1728 to remove any confusion, with an example! I decided not to implement a new
does that. But I could. Last 10 new commits:
|
comment:9
There are lots of commits listed above, none of which is mine. The relevant one, which you can see by clicking on the branch name, is dc07e494c5230bef1dd7e1a0df351194a03acb36 . |
comment:10
the |
Changed branch from u/cremona/ticket/14060 to u/wuthrich/ticket/14060 |
comment:11
I rebased it to the 6.1.beta6 in the hope that the extra merge commits above do not show anymore (even if they are harmless. Since all test then pass for me, I give it a positive review. New commits:
|
Reviewer: Chris Wuthrich |
comment:12
By the way, I believe there are 4 spaces before the ..note. No ? At least the html output seems ok. |
comment:13
Replying to @categorie:
I don't know, I thought that not warnings were produced when building the docs but have forgotten. Thanks for the review! |
We need a better implementation of minimal_quadratic_twist(), for example if the conductor is square-free then there is no need to do so much work as is currently done. Additionally, when j(E)=0 or 1728 the curve returned is a minimal quadratic twist, but not necessarily the minimal twist, and it would be a good thing for the documentation to make this clear.
CC: @categorie
Component: elliptic curves
Keywords: pari precision
Author: John Cremona
Branch/Commit: u/wuthrich/ticket/14060 @
634ab95
Reviewer: Chris Wuthrich
Issue created by migration from https://trac.sagemath.org/ticket/14060
The text was updated successfully, but these errors were encountered: