-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
MOI looking for MIP in LP problem #1554
Comments
Starting values are not implemented for ECOS yet, the error message says that if you use MOI master :) cc @IssamT for Clp |
@blegat thanks, I am using the tagged version of JuMP. Something happened that all the LP solvers (that support start values) broke. |
@jd-lara, could you please send a MWE reproducing this error? |
Oh, I just noticed that you are using MOI. Clp and GLPK implement the LQOI interface and apparently they haven't implemented ECOS gives a different error because it doesn't use LQOI for implementing MOI. |
While trying to reproduce this error, I had a different error because I didn't set the
The following example raises that error: using JuMP
using Clp
m = Model(with_optimizer(Clp.Optimizer))
@variable(m, 0 <= x <= 1)
@variable(m, 0 <= y <= 1)
@variable(m, 0 <= z <= 1, start=1.0)
@constraint(m, x + y + z >= 1)
@objective(m, Min, 2x + y + z)
JuMP.optimize!(m) The error I was getting is due to the fact MOI's When defining the start value of all variables, then I get the same error in the issue and it should be fixed with this PR jump-dev/Clp.jl#44 |
See #1460 |
Is this now a duplicate of #1460? |
I have opened issues to corresponding repo: We can close this. |
I am trying to solve an LP problem with several linear solvers, GLPK and Clp and I am getting this error as if the solver was trying to find Integer Variables. However, if I use Ipopt then the model runs which indicate is not a model specification problem. I have checked that all my variables have a start value consistently also.
Trying with ECOS gives a different error
The text was updated successfully, but these errors were encountered: