Documentation

Next: GRBaddrangeconstrs Up: Model Creation and Modification Previous: GRBaddqpterms

GRBaddrangeconstr

Add a new range constraint to an existing model. A range constraint states that the value of the input expression must be between the specified lower and upper bounds in any solution. Note that the new constraint won't actually be added until the next call to GRBoptimize or GRBupdatemodel.

Return value:

A non-zero return value indicates that a problem occurred while adding the constraint. Refer to the Error Code table for a list of possible return values. Details on the error can be obtained by calling GRBgeterrormsg.

Arguments:

model: The model to which the new constraint should be added.

numnz: The number of non-zero coefficients in the linear expression.

cind: Variable indices for non-zero values in the linear expression.

cval: Numerical values for non-zero values in the linear expression.

lower: Lower bound on linear expression.

upper: Upper bound on linear expression.

constrname: Name for the new constraint. This argument can be NULL, in which case the constraint is given a default name.

Important notes:

Note that adding a range constraint to the model adds both a new constraint and a new variable. If you are keeping a count of the variables in the model, remember to add one whenever you add a range.

Note also that range constraints are stored internally as equality constraints. We use the extra variable that is added with a range constraint to capture the range information. Thus, the Sense attribute on a range constraint will always be GRB_EQUAL.

Example usage:

  int    ind[] = {1, 3, 4};
  double val[] = {1.0, 2.0, 3.0};
  /* 1 <= x1 + 2 x3 + 3 x4 <= 2 */
  error = GRBaddrangeconstr(model, 3, ind, val, 1.0, 2.0, "NewRange");

---

Next: GRBaddrangeconstrs Up: Model Creation and Modification Previous: GRBaddqpterms