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
This is a follow-up on #20301. #20296 provides a way to select a suitable solver by its base_ring.
Polyhedron.to_linear_program should do that.
Note, for exact polyhedra, this will change the behavior of to_linear_program from inexact computation to exact computation, which will be much slower (but note, speed is irrelevant for this method, because when the Polyhedron was set up, already the double description has been computed eagerly.)
To restore the old behavior, the user would need to pass an explicit base_ring=RDF or solver=... argument to to_linear_program.
(The patch adds many examples that illustrate this.)
This is a follow-up on #20301.
#20296 provides a way to select a suitable solver by its
base_ring
.Polyhedron.to_linear_program
should do that.Note, for exact polyhedra, this will change the behavior of
to_linear_program
from inexact computation to exact computation, which will be much slower (but note, speed is irrelevant for this method, because when thePolyhedron
was set up, already the double description has been computed eagerly.)To restore the old behavior, the user would need to pass an explicit
base_ring=RDF
orsolver=...
argument toto_linear_program
.(The patch adds many examples that illustrate this.)
CC: @dimpase @videlec @novoselt
Component: geometry
Author: Matthias Koeppe
Branch/Commit:
7b7aa5e
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/20415
The text was updated successfully, but these errors were encountered: