Originally posted by: SystemAdmin
Hi,
We build up our model constraints in code from user input. A recent addition has been a quadratic constraint representing a "least square" matching constraint. This has given us problems when we come to solve the model. We solve the LP problem first and then switch to a MIP and solve again.
I've stripped the model right back to include just the new quadratic constraint (see x.lp, attached) and have observed the following:
If I use the interactive optimiser, I can load the model, optimise it, switch the problem type to miqcp and run mipopt to get an optimised solution.
If I write a most basic code snippet in CSharp to import the model and call Solve, the method returns quickly with false and the status is set to Unknown.
Relaxing the RHS of the constraint even by by 0.0001 allows the model to solve as an LP using the API. However, this is a very basic model whereas the real-life ones will include many more vars and larger weightings so I'd like to understand what the issue is before allowing tolerances on the RHS when the user doesn't actually specify one - they can specify an exact match.
Not sure if it's related, but we've also noticed some models that do solve taking significantly longer to solve using the API as opposed to interactively.
Thanks in advance,
Neil
#CPLEXOptimizers#DecisionOptimization