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
Bug in charpoly over discrete valuation rings #31753
Comments
Branch: u/caruso/charpoly |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Xavier Caruso |
Reviewer: Samuel Lelièvre, ... |
comment:5
a. The patchbot reports an incorrect Trac link. To fix it: - We check that trac:`31753` is resolved::
+ We check that :trac:`31753` is resolved:: b. Your fix for the bug seems to consist in removing Can you explain why that caused a problem, and why this is a good solution? But probably someone who knows more Cython than me should review that part. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Replying to @slel:
It's just because |
comment:9
Right, Still, about - cdef Matrix_generic_dense c
- cdef RingElement pivot, inv, scalar
+ cdef RingElement entry, pivot, inv, scalar Commit 28a35a97 |
comment:10
Replying to @slel:
Good point! |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Since this fixes a bug, maybe it can still go in Sage 9.3. |
This comment has been minimized.
This comment has been minimized.
Changed reviewer from Samuel Lelièvre, ... to Samuel Lelièvre |
Changed keywords from characteristic polynomial to characteristic polynomial, charpoly |
comment:14
milestone to 9.4, as 9.3 has been released |
Changed branch from u/caruso/charpoly to |
There is a bug in the computation of the characteristic polynomial over a discrete valuation ring.
Expected:
This ticket fixes that.
CC: @sagetrac-rpages @slel
Component: linear algebra
Keywords: characteristic polynomial, charpoly
Author: Xavier Caruso
Branch/Commit:
41b3880
Reviewer: Samuel Lelièvre
Issue created by migration from https://trac.sagemath.org/ticket/31753
The text was updated successfully, but these errors were encountered: