Gurobi Error 10005 is seen on submitting lazy constraint also when cb_where == GRB_CB_MIPNODE

odow · May 17, 2025, 8:27pm

At a MIPNODE you need to check the solver’s status.

See the Gurobi.jl documentation jump-dev/Gurobi.jl · JuMP and this part of the source

src/MOI_wrapper/MOI_callbacks.jl

18666a049


      
          elseif cb_where == GRB_CB_MIPNODE
              resultP = Ref{Cint}()
              GRBcbget(cb_data, cb_where, GRB_CB_MIPNODE_STATUS, resultP)
              if resultP[] != GRB_OPTIMAL
                  return  # Solution is something other than optimal.
              end
              load_callback_variable_primal(cb_data, cb_where)

Topic		Replies	Views
Branching solution accepted although it violates presently added lazy constraints Optimization (Mathematical) jump , gurobi	5	738	May 7, 2022
Gurobi Lazyconstraints with JuMP 0.21 Optimization (Mathematical)	2	811	May 21, 2020
Callback jump MOI interface lazy constraints are not cutting the solution properly Optimization (Mathematical) jump , optimization , lazy-constraint	1	498	April 8, 2022
Lazy constraint callback issue with GLPK Optimization (Mathematical) question , jump , optim , optimization	5	838	April 5, 2021
Lazy constraints with callback in gurobi Optimization (Mathematical)	1	851	December 20, 2021

Gurobi Error 10005 is seen on submitting lazy constraint also when cb_where == GRB_CB_MIPNODE

Related topics