MIPCOMPONENTS
|
Description
|
Determines whether disconnected components in a MIP should be solved as separate MIPs. There can be significant performence benefits from solving disconnected components individual instead of being part of the main branch-and-bound search.
|
||||||
|
Type
|
Integer
|
||||||
|
Values
|
|
||||||
|
Default value
|
-1
|
||||||
|
Note
|
If there are no constraints linking two variables, either directly or indirectly through other variables, they are said to belong to two separate disconnected components. When a problem contains disconnected components of signficant size, it can be advantageous to solve each component as a separate MIP. When significant disconnected components are detected in the problem, the solver will switch to a different solve mode where each component is solved separately. This switch will happen after the root node processing has completed and when the solve is about to enter the branch-and-bound search.
|
||||||
|
Note
|
Solving disconnected components separately is not compatible with many callbacks that can be used for modifying the branch-and-bound search. Setting any of the following callbacks will automatically disable the separate solving of disconnected components:
XPRSaddcboptnode,
XPRSaddcbprenode,
XPRSaddcbcutmgr,
XPRSaddcbestimate,
XPRSaddcbsepnode,
XPRSaddcbchgbranch,
XPRSaddcbchgbranchobject
|
||||||
|
Note
|
Solving disconnected components separately is not compatible with concurrent MIP solves. If concurrent MIP solves has been turned off, disconnected components will be solved as part of the standard branch-and-bound search in each concurrent solve.
|
||||||
|
Note
|
Disabling MIP dual reductions through
MIPDUALREDUCTIONS will also disable the separate solve of disconnected components.
|
||||||
|
Affects routines
|
|||||||
|
See also
|