-
Notifications
You must be signed in to change notification settings - Fork 30
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
Detection of non-linear/non-convex problem #274
Comments
Is this on the latest tagged version or the latest |
Ah it's Xpress.jl/src/MOI/MOI_wrapper.jl Lines 2910 to 2916 in 60ae1dd
|
I think the issue was that Lines 479 to 482 in 60ae1dd
and some users of Xpress.jl are still stuck on quite outdated versions of Xpress. |
That is a pretty old version of Xpress to support. But is it not possible to have code that checks the version of Xpress available and adjusts accordingly? With the current implementation we do not get access to the capabilities of the global solver for nonconvex quadratic problems (nor MIQCQPs where the quadratic part defines a non-convex region). |
Yeah, we can probably do that. Especially now that we have CI for old and new versions.
I won't name and shame the customer... |
The current implementation calls a different optimization routine depending on internal classification schemes
This does not seem to work properly for non-convex quadratic problems which are not set as having nonlinear constraints and thus failing when calling
XPRSlpoptimize
. Here is a small example that fails:Instead of relying on an internal classification scheme would it not be better to let the choice of algorithm be left for Xpress using the more general
XPRSoptimize
function? The type of optimization used can then be queried afterwards using theXPRS_OPTIMIZETYPEUSED
-attribute if this is needed before solution retrieval.The text was updated successfully, but these errors were encountered: