Originally posted by: SystemAdmin

I noticed that the CPLEX 11.2 manual says that the additional items like 'Variables', 'B', 'Parent' and 'Depth' for conventional branch & cut are not available for dynamic search. Does that also mean that there is no other method that I can use to know these information when cplex uses dynamic search for MIP search method? What about other versions beyond 11.2? Furthermore, would anyone like to talk a little bit more about dynamic search? What is the physiology behind this method? What logic is it following? Thank you very much for any help.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Dynamic search is a bit different than traditional branch-and-bound in the way the search tree is constructed and traversed. Therefore, some notions like "branching variable", "parent node", or "depth" may not have a meaning in some situations, at least not one that is consistent with what the user would expect when he thinks in terms of traditional branch-and-bound.

Regarding what dynamic search really is, we cannot say much more than "it is a different search strategy, and some user assumptions based on traditional b&b are no longer valid".

Tobias
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

But if I switched to traditional search method, could I use any method like 'callback' to know the variable name branched on?
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Yes, you can. And you will then also be able to find the information in the 'cplex.log' file.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Is IloCPlex::NodeCallback what I should use if I used C++ API? What method of this class should I use? Thank you very much.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

In principle you would use the branch callback. But I am not sure whether you can extract the necessary information from the C++ API. Namely, the whole search procedure takes place on the presolved model. This model can only be accessed through the C API. Consequently, CPLEX may branch on a (presolved) variable that you cannot even interpret correctly in the original model that is accessible from the C++ API.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Please look at this thread. It discusses in great detail how to keep track of the variables on which you/CPLEX branched.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Thanks for your information, I will read through it.
#CPLEXOptimizers
#DecisionOptimization