Parameter Examples#

Gurobi parameter handling is designed to be orthogonal, meaning that you only need to use a small number of routines to work with a large number of parameters. In particular:

  • The names and meanings of the various Gurobi parameters remain constant across the different programming language APIs, although some decoration is required in each language.

  • Given the type of a parameter (double, integer, etc.) and the programming language you wish to use it from, you simply need to identify the appropriate routine for that parameter type in that language in order to query or modify that parameter.

One important note about integer-valued parameters: while the maximum value that can be stored in a signed integer is \(2^{31}-1\), we use a MAXINT value of 2,000,000,000. Attempting to set an integer parameter to a value larger than this maximum will produce an error.

Refer to the following for detailed examples of how to work with parameters from our various APIs:

You can also browse our Examples to get a better sense of how to use our parameter interface.

The C interface defines a symbolic constant for each parameter. The symbolic constant name is prefixed by GRB_type_PAR_, where type is either INT, DBL, or STR. This is followed by the capitalized parameter name. For example, the symbolic constant for the integer Threads parameter (found in C header file gurobi_c.h) is:

#define GRB_INT_PAR_THREADS "Threads"

The routine you use to modify a parameter value depends on the type of the parameter. For a double-valued parameter, you would use GRBsetdblparam.

Note that a model gets its own copy of the environment when it is created. Changes to the original environment have no effect on the copy, and vice versa. Use GRBgetenv to retrieve the environment associated with a model if you would like to change the parameter value for that model.

To set the TimeLimit parameter for a model, you’d do:

error = GRBsetdblparam(GRBgetenv(model), GRB_DBL_PAR_TIMELIMIT, 100.0);

If you’d prefer to use a string for the parameter name, you can also do:

error = GRBsetdblparam(GRBgetenv(model), "TimeLimit", 100.0);

The case of the string is ignored, as are underscores. Thus, TimeLimit and TIME_LIMIT are equivalent.

Use GRBgetdblparam to query the current value of a (double) parameter:

double currentvalue;
error = GRBgetdblparam(modelenv, "TimeLimit", &currentvalue);