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