-
Notifications
You must be signed in to change notification settings - Fork 19
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
unexpected behaivour with polytope package, ( probably a bug , but not sure ) #93
Comments
You wrote "unexpected numbers". Do you know what the return value of |
thank you Herr @slivingston for your comment. yes, I know what it should be. The dimension is 4. The aexs range from 0 to 0.5. the bounding box should range up to only 0.18 and 0.12 at maximum., along the 3rd and 4th directions. But I see this is inf. I am happy to share more info if you need it in any case thank you Best regards |
The polytope given above is unbounded. For unbounded polyhedra, a vertex representation does not exist, hence If you expect it to have a bounding box with dimensions at most 0.18, 0.12 along the 3rd and 4th direction, you might want to double check how you specify your polytopic constraints. As a simple counterexample, you can consider the following point: |
That is the problem I am facing in my program. I try to solve polytope for different orders, let us say order l = 1, 2, 3, 4 .... The polytope
is the solution space after taking orders l = 1, 2, 3 into the calculation. The intersection operation is used to find the solution space. I opened another discussion #94 , regarding the intersection operation. The above polytope is made using &. still, I have to debug where the problem arises from finally, I can use pc.bounding_box to get the bound box and say polytope is bounded or open. does polytope provide any other option to cross-check whether a given polytope is bounded or not? like polytope.is_valid? Thank youBest regards |
Dear Developers and users,
recently I have been facing an issue with using the polytope package. I have A and b matrixes,
and create a polytope 'p' as
For this polytope, I get some unwanted numbers when I calculate extreme points as
This gives
The polytope seems to be exploding along some directions ( so the values along the 3rd and 4th columns of pc.extreme(p) are 3.31721e+13 ). If I redo the calculation, sometimes the
pc.extreme
returnsIn my view pc.extreme(p) contains unwanted or unexpected numbers.
because doing
returns
But the
returns
some weird things are happening with this polytope p or polytope package. Any leads or suggestions are highly appreciated
Thank you for your time on this question
Best regards
Muthu Vallinayagam
Research, Institute of Experimental Physics
TU Freiberg
Germany
The text was updated successfully, but these errors were encountered: