type_conflict.h
Go to the documentation of this file.
34 /*---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2*/
48 typedef struct SCIP_Conflicthdlr SCIP_CONFLICTHDLR; /**< conflict handler to process conflict sets */
51 typedef struct SCIP_ProofSet SCIP_PROOFSET; /**< set of variables and coefficients describing a proof-constraint of type a^Tx <= rhs */
112 /** solving process initialization method of conflict handler (called when branch and bound process is about to begin)
114 * This method is called when the presolving was finished and the branch and bound process is about to begin.
121 #define SCIP_DECL_CONFLICTINITSOL(x) SCIP_RETCODE x (SCIP* scip, SCIP_CONFLICTHDLR* conflicthdlr)
123 /** solving process deinitialization method of conflict handler (called before branch and bound process data is freed)
132 #define SCIP_DECL_CONFLICTEXITSOL(x) SCIP_RETCODE x (SCIP* scip, SCIP_CONFLICTHDLR* conflicthdlr)
137 * The conflict handler may update its data accordingly and create a constraint out of the conflict set.
138 * If the parameter "resolved" is set, the conflict handler should not create a constraint, because
140 * The bounds in the conflict set lead to a conflict (i.e. an infeasibility) when all enforced at the same time.
141 * Thus, a feasible conflict constraint must demand that at least one of the variables in the conflict
142 * set violates its corresponding bound, i.e., fulfills the negation of the bound change in the conflict set.
143 * For continuous variables, the negation has to be defined in a relaxed way: if, e.g., the bound in the conflict
146 * buffer, that may be modified at any time by SCIP. The user must copy the needed information from the
148 * (S)he should not keep a pointer to the array or pointers to the single bdchginfos in the array, because these
155 * - validnode : node at which the conflict constraint is valid (should be passed to SCIPaddConsNode())
159 * -.primalbound : the current primal bound, or -infininity if the conflict arises from an infeasible LP
161 * - local : is the conflict set only valid locally, i.e., should the constraint be created as local constraint?
169 * - SCIP_DIDNOTFIND : the conflict handler could not create a constraint out of the conflict set
172 #define SCIP_DECL_CONFLICTEXEC(x) SCIP_RETCODE x (SCIP* scip, SCIP_CONFLICTHDLR* conflicthdlr, SCIP_NODE* node, \
173 SCIP_NODE* validnode, SCIP_BDCHGINFO** bdchginfos, SCIP_Real* relaxedbds, int nbdchginfos, SCIP_CONFTYPE conftype, \
174 SCIP_Bool cutoffinvolved, SCIP_Bool separate, SCIP_Bool local, SCIP_Bool dynamic, SCIP_Bool removable, \
Definition: type_conflict.h:61
Definition: type_conflict.h:70
Definition: type_conflict.h:59
Definition: type_conflict.h:72
Definition: struct_conflict.h:113
type definitions for return codes for SCIP methods
Definition: type_conflict.h:73
Definition: struct_conflict.h:49
Definition: type_conflict.h:63
Definition: struct_conflict.h:68
Definition: type_conflict.h:62
struct SCIP_ConflicthdlrData SCIP_CONFLICTHDLRDATA
Definition: type_conflict.h:49
type definitions for problem variables
Definition: type_conflict.h:71
result codes for SCIP callback methods
Definition: type_conflict.h:58
Definition: struct_conflict.h:102
Definition: struct_conflict.h:90
common defines and data types used in all packages of SCIP
Definition: type_conflict.h:60