Originally posted by: oscaralive

Hi all,

I have a problem with MIPInfoCallback. Using a vector of times I successively print the best Integer obtained using a myMIPInfocallback I have written. However, at some step (I don't know why) it stops printing. Here is an example. MP means my measuring points in the time vector. it stops at incumbentVal (Best Integer) 81, whereas the solution is found at 49 as you can see below. Why does the callback function stop writing?
MP24.0 827
0 0 47.4094 33 81.0000 GUBcuts: 1 355 41.47%
MP30.0 842
0 0 47.4094 35 81.0000 Cuts: 3 357 41.47%

• 0+ 0 65.0000 47.4094 357 27.06%
• 0+ 0 57.0000 47.4094 357 16.83%
• 0+ 0 54.0000 47.4094 357 12.20%

Repeating presolve.
Tried aggregator 1 time.
MIP Presolve eliminated 0 rows and 4679 columns.
MIP Presolve modified 676 coefficients.
Reduced MIP has 47 rows, 994 columns, and 2790 nonzeros.
Reduced MIP has 993 binaries, 1 generals, 0 SOSs, and 0 indicators.
Tried aggregator 1 time.
Represolve time = 0.06 sec.
Clique table members: 34.
MIP emphasis: balance optimality and feasibility.
MIP search method: dynamic search.
Parallel mode: none, using 1 thread.
Root relaxation solution time = 0.02 sec.

Nodes Cuts/
Node Left Objective IInf Best Integer Best Node ItCnt Gap

• 0+ 0 54.0000 47.4094 357 12.20%

0 0 48.7143 15 54.0000 48.7143 523 9.79%

• 0+ 0 49.0000 48.7143 523 0.58%

0 0 cutoff 49.0000 48.7143 523 0.58%
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

The MIP Info Callback is not necessarily called for each new incumbent. But it should be called at least once at the end of the optimization. So, you should get the final incumbent. If this is not the case, I think that this would be a bug in CPLEX.

Tobias
#CPLEXOptimizers
#DecisionOptimization