-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
We encountered a difference between the best found solution in the solver log for Xpress 9.2:
Concurrent statistics:
Dual: 116729 simplex iterations, 64.75s
Barrier: 500 barrier and 63482 simplex iterations, 192.05s
Barrier used 11 threads 6 cores
Barrier used AVX support, crossover used 8 thread
Optimal solution found
Its Obj Value S Ninf Nneg Sum Inf
116729 33552689.03 P 0 0 .000000
Dual solved problem
116729 simplex iterations in 192.09 seconds at time 194
Final objective : 3.355268902586088e+07
Max primal violation (abs/rel) : 0.0 / 0.0
Max dual violation (abs/rel) : 4.547e-13 / 1.238e-14
Max complementarity viol. (abs/rel) : 0.0 / 0.0
High attention level predicted from matrix features
Starting root cutting & heuristics
Deterministic mode with up to 1 additional thread
Its Type BestSoln BestBound Sols Add Del G
k 35670343.87 33552689.03 1 5.
Heuristic search 'R' started
Heuristic R running (50000 LP iterations in 10.1 seconds)
R 33552689.03 33552689.03 2 -0.
STOPPING - MIPRELSTOP target reached (MIPRELSTOP=0.01 gap=-2
Heuristic search 'R' stopped
*** Search completed ***
Uncrunching matrix
Final MIP objective : 3.355268902585221e+07
Final MIP bound : 3.355268902586088e+07
Solution time / primaldual integral : 301.62s/ 70.306447
Number of solutions found / nodes : 2 / 1
Max primal violation (abs/rel) : 9.095e-13 / 8.633e-13
Max integer violation (abs ) : 1.912e-07
And what's in the the solution summary for our instance (copy-pasted from the REPL):
julia> solution_summary(model)
* Solver : Xpress
* Status
Result count : 1
Termination status : OPTIMAL
Message from the solver:
"6 Global search complete - integer solution found ( XPRS_MIP_OPTIMAL). - MIP gap is sufficiently small"
* Candidate solution (result 1)
Primal status : FEASIBLE_POINT
Dual status : NO_SOLUTION
Objective value : 3.56703e+07
Objective bound : 3.35527e+07
Relative gap : 5.93674e-02
Dual objective value : 3.56703e+07
* Work counters
Solve time (sec) : 3.09471e+02 It appears to return the first solution found instead of the optimal solution for our MILP.
Metadata
Metadata
Assignees
Labels
No labels