Originally posted by: SystemAdmin
Does the act of attaching a HeuristicCallback cause CPLEX to suppress any default heuristics or change any presolve settings? I have a Java program with an incumbent callback, to which I added a heuristic callback. The heuristic callback will try to inject a new solution fi and only if the incumbent callback sets a flag.
On my test problem, the code without the heuristic callback hits at least one or two nodes where the incumbent callback sets the flags, and it's consistent (same outcome every time I run it). With the heuristic callback attached, the path through the search tree apparently changes and the flag never gets set -- which means the heuristic callback never does anything (just exits each time). So the heuristic callback does not actively change the search path, but its mere presence seems to do so (which makes debugging a problem).
/Paul
Mathematicians are like Frenchmen: whenever you say something to them, they translate it into their own language, and at once it is something entirely different. (Goethe)
#CPLEXOptimizers#DecisionOptimization