-
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
Mismatch between solution returned and best found solution in solver log #210
Comments
cc @odow |
I've a bit limited debugging this because I only have the community license, and this problem is too big, but... First impressionIn JuMP's Xpress.jl/src/MOI/MOI_wrapper.jl Lines 3196 to 3200 in 4d70faf
There's not a lot to go wrong here, so if this doesn't return the optimal solution, but the first solution from
then it seems that this is a bug in Xpress. (Unless we need to set some options for returning multiple solutions?) More infoHere's the MPS file that Maddie sent me via email: Could you: Provide the output of Provide the versions of Xpress that you tried (9.2 buggy, others not so?) Try running with heuristics turned off Confirm that we can reproduce this outside of REopt with just the MPS file. import JuMP, Xpress
model = JuMP.read_from_file("problematic_mps.mps")
JuMP.set_optimizer(model, Xpress.Optimizer)
JuMP.set_attribute(model, "MIPRELSTOP", 0.01) # Or whatever option you set?
JuMP.optimize!(model)
JuMP.solution_summary(model) |
So this doesn't seem related to multiple solutions, because there's a special set of functions for that:
So I'm going to guess that this is a bug in Xpress. |
@joaquimg could you try reproducing this? The community license is too small. |
So now that I've spent a bit of time in the code, I really think this is an upstream issue. I can't see how this would be a bug in Xpress.jl. |
I ran the basic thing it was taking forever:
Then a I ran with
|
We encountered a difference between the best found solution in the solver log for Xpress 9.2:
And what's in the the solution summary for our instance (copy-pasted from the REPL):
It appears to return the first solution found instead of the optimal solution for our MILP.
The text was updated successfully, but these errors were encountered: