-
Notifications
You must be signed in to change notification settings - Fork 27
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
Removing constraints of empty polyhedron results in non-empty set #146
Comments
Is it not even worse if the removal of redundant constraints from an empty set results in a non-empty set? |
@schillic true, i've reopened this issue with a different title to suggest that some action should be taken, either make it clear in |
Isn't the bug in CDD ? |
The problem also occurs with the "default library". (EDIT: simplified the numbers) for backend in [CDDLib.Library(), default_library(2, Float64)]
p = polyhedron(hrep([HalfSpace([1.0, 0.0], 0.3),
HalfSpace([-1.0, 0.0], -0.2),
HalfSpace([0.0, 1.0], 0.1),
HalfSpace([0.0, -1.0], 0.1)]), backend)
q = polyhedron(hrep([HalfSpace([-1.0, 0.0], 0.0),
HalfSpace([-0.7, -1.0], 0.0),
HalfSpace([0.7, 1.0], 0.0)]), backend)
P = Polyhedra.intersect(p, q)
Polyhedra.removehredundancy!(P)
println(P)
end HyperPlane([1.0, 0.0], 0.3)
∩ HyperPlane([-1.0, 0.0], -0.2)
∩ HyperPlane([0.0, 1.0], 0.1)
HyperPlane([0.7, 1.0], 0.0) : |
The following example shows what i think is a bug in
removehredundancy!
:(reported here @schillic)
(EDITED)
I had a quick look at a workaround using a Polyhedra.Ray:
i just plotted this in geogebra; the intersection is actually empty :)
indeed:
and
given this, i take back my assumption that
removehredundancy!
is buggy.The text was updated successfully, but these errors were encountered: