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
Local components bug finding minimal twist #13158
Comments
Author: David Loeffer |
comment:6
Somehow, this sat idle for 3 years despite the fact that the fix is about 2 lines! It turns out that the code relies on the assumption that the trace of the type space down to the minimal level is simple, but if f is of CM type it can be the direct sum of two simple modules of opposite sign. New commits:
|
Commit: |
Changed branch from u/davidloeffler/local_components_bug_finding_minimal_twist to public/ticket/13158 |
Reviewer: Frédéric Chapoton |
comment:8
Thanks for the review! The patchbot seems a bit confused, but I'm sure it'll catch up shortly :-) |
Changed branch from public/ticket/13158 to |
Changed author from David Loeffer to David Loeffler |
Changed commit from |
The following is from an email of François Brunault:
I got the following error when trying to compute minimal twists in Sage. Here f is the newform attached to the elliptic curve 256a1, and the minimal twist of f has level 64.
Best,
François
Component: modular forms
Keywords: local components
Author: David Loeffler
Branch:
3577e02
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/13158
The text was updated successfully, but these errors were encountered: