Originally posted by: DianaHuerta
Thank you!, your answers helped me a lot. Now I have my SAV file complete =).
Now I have detected one instance where the optimum is different. If I solve my model (adding the lazy&callbacks constraints during the branch & cut process) the optimal solution is different than the obtained using the import function.
The optimal solution reported by the B&C is:
429(1) 97.189 366.85 0 64 64 5623.11 5626 0.000513797
430(0) 97.204 367.264 0 64 64 5626 5626 0
Solution status = Optimal
Solution value = 5626
Number of B&B nodes = 430
I would like to know how I can give to cplex that solution in order to obtain the same one when I import it (or at least to know if something is happening or if a cut is violated for the "optimal" B&C solution).
I have tried the following things:
When I solve the B&C, I save the final solution in a SOL file (and also have tested with the MST file).
Using the first one I have the following:
Warning, line 28: Constraint index '2' out of range.
Warning, line 29: Constraint index '3' out of range.
Warning, line 30: Constraint index '4' out of range.
Warning, line 31: Constraint index '5' out of range.
Warning, line 32: Constraint index '6' out of range.
Warning, line 33: Constraint index '7' out of range.
Warning, line 34: Constraint index '8' out of range.
Warning, line 35: Constraint index '9' out of range.
Warning, line 36: Constraint index '10' out of range.
Warning, line 37: Constraint index '11' out of range.
Warning, line 38: Constraint index '12' out of range.
Warning, line 39: Constraint index '13' out of range.
Warning, line 40: Constraint index '14' out of range.
Warning, line 41: Constraint index '15' out of range.
Warning, line 42: Constraint index '16' out of range.
Warning, line 43: Constraint index '17' out of range.
Warning, line 44: Constraint index '18' out of range.
Warning, line 45: Constraint index '19' out of range.
395 warnings not printed.
Default row names c1, c2 ... being created.
EpMrk = 0.01
Solution status = Optimal
Solution value = 5766.54
Maximum bound violation = 0
Using the second one I obtain:
Concert exception caught: CPLEX Error 3003: Not a mixed-integer problem. *
* I have read that this kind of problem appears because the solution seems to be not feasible. I have tried this using the interactive cplex and it can be solved but the optimal value is 5766.54 (the same as if I use the SOL file using the Concert API). Also, I have seen that this message: "Warning: No solution found from 1 MIP starts." appears in the interactive application. I have disabled some features of cplex in order to avoid to fix the initial solution and see why the MIP start is ignored, but I had no success until now.
Any idea will be appreciated =).
Kind regards.
Diana
#CPLEXOptimizers#DecisionOptimization