Originally posted by: SystemAdmin
Thanks again for reporting this problem. This is a numerical bug that we have in the code since ages and which is triggered for some weird reason by your problem instance. The issue is inside probing, and will be fixed in the next release. You should be able to get the correct answer by disabling probing. This can be done using
set mip strategy probing -1
in the interactive CPLEX shell.
Tobias
#CPLEXOptimizers#DecisionOptimization