You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I added rawHilbertBasis from Normaliz I also changed latticePoints Polyhedron to use it instead, which is in turn used by monomials ToricDivisor. This improved the speed greatly because Normaliz parallelizes this computation.
I realized this means we can also significantly improve multigraded basis in this case. This is kind of already implemented in basis' in the Truncations package without any toric assumptions.
One problem is that the order of monomials found this way may be different than the engine algorithm. @mikestillman is this a problem? I recall running into this #2810 as well.
Also, should this be implemented in the top level, or is it worth changing basis0_multi_graded in matrix-kbasis.cpp to directly use Normaliz via rawHilbertBasis?
When I added
rawHilbertBasis
from Normaliz I also changedlatticePoints Polyhedron
to use it instead, which is in turn used bymonomials ToricDivisor
. This improved the speed greatly because Normaliz parallelizes this computation.I realized this means we can also significantly improve multigraded basis in this case. This is kind of already implemented in
basis'
in the Truncations package without any toric assumptions.One problem is that the order of monomials found this way may be different than the engine algorithm. @mikestillman is this a problem? I recall running into this #2810 as well.
Also, should this be implemented in the top level, or is it worth changing
basis0_multi_graded
inmatrix-kbasis.cpp
to directly use Normaliz viarawHilbertBasis
?cc: @jkyang92
The text was updated successfully, but these errors were encountered: