-
Notifications
You must be signed in to change notification settings - Fork 29
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
PanicException: assertion left == right
failed
#127
Comments
It looks like that error is thrown when there is a mismatch between the dimension of Edit: even if the above is the issue, please leave this open since that is not a nice way for the solver to fail. Probably better for us rewrite some of these input checking assertions so that they return clearer error to the user on solver initialisation. |
The
Here is the context for reference. |
The cones appear to be compatible, although the total dimension (2432) is lower than both sides of the assertion that failed. In version 0.8.0 we reimplemented the preprocessing step that eliminates infinite bounds, so perhaps an error was introduced there. Does |
Yes it does 🎯
|
OK, thank you for confirming. I think this must be a bug introduced in the v0.8 version of the presolve. I will make a fix and release patched version as soon as I can, but probably not for a week or two. |
Hi and thanks again for maintaining this open source solver 😃 I noticed the following exception thrown by Clarabel on the
QUADCMPC1
problem of the free-for-all QP test set:I checked quickly that
A_stack.shape=(2432, 768)
andb_stack.shape=(2432,)
(could be "left" and "right"?). Other solvers like OSQP solve the problem successfully.Sorry I don't have the time right now to make a reproducer that does not depend on the benchmarking library, but the exception should be reproducible (after conda/PyPI installing
qpbenchmark
) by:$ python free_for_all.py run --solver clarabel --problem QUADCMPC1
Finally I noticed that Clarabel 0.7.0 does not raise the exception, while Clarabel 0.8.0 does.
Hoping this helps!
The text was updated successfully, but these errors were encountered: