-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Normaliz cone from precomputed data has lattice messed up #30891
Comments
comment:1
Normaliz data for
Normaliz data for
The volume is probably a usage error, I did not consider the case where a "cube" in the generated lattice has volume not equal to Ok, the other issue probably as well. This raises a simple question in sage: Given rational vectors. How do I calculate integer vectors that generate the induced lattice? Actually the given vectors or integer, but for the mathematical question, I consider them to be rational. |
Changed upstream from Not yet reported upstream; Will do shortly. to none |
comment:3
I guess the solution to the second part also solves the first part, because in case of the volume the generated lattice is always the entire lattice (otherwise the "ambient" volume is zero anyway). |
Author: David Roe, Jonathan Kliem |
Branch: public/30891 |
Commit: |
New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Changed branch from public/30891 to public/30891-reb |
Reviewer: Matthias Koeppe |
comment:9
Thank you. |
Changed branch from public/30891-reb to |
The problem is that we should take the saturation instead of the basis of the row space. In the example above the quotient of the ambient lattice with the computed basis was not torsion-free.
CC: @jplab @LaisRast @mkoeppe
Component: geometry
Keywords: normaliz, polytope
Author: David Roe, Jonathan Kliem
Branch/Commit:
bcc7ea6
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/30891
The text was updated successfully, but these errors were encountered: