Originally posted by: bindasmariner
Thanks Faisal. I have tried running the maximization MILP after modifying the upper/lower cutoffs as 9.75 and 5.5 in the MILP>tolerances section of my .opf file. I would like to show you the starting engine log of the run:
Node Left Objective IInf Best Integer Best Node ItCnt Gap
0 0 17.8591 45 17.8591 126
0 0 14.9167 48 Cuts: 98 296
0 0 14.9167 48 Cuts: 52 412
0 0 14.9167 40 Cuts: 45 534
0 0 14.9167 38 Cuts: 20 657
0 2 14.9167 38 14.7500 657
100 66 infeasible 14.7500 5732
200 122 12.5510 25 14.7500 9312
300 181 13.7500 29 14.7500 12780
400 256 14.6429 28 14.7500 15957
500 317 infeasible 14.7500 19487
600 316 13.7500 23 14.7500 26240
700 335 infeasible 14.7500 31647
800 336 13.6262 27 14.7500 38991
900 329 12.4583 22 14.7500 45476
1000 319 13.9892 13 14.7500 53821
Elapsed time = 28.34 sec. (tree size = 0.17 MB, solutions = 0)
I guess this method is not working as an upper/lower bound, otherwise why would the LP solution start with 17 or 14. it should directly jump to 9.75 and below.
I will surely try the warm-start method as suggested.
Regards
Saurabh
#DecisionOptimization#OPLusingCPLEXOptimizer