In the parameter table, each parameter has a name (that is, a symbolic constant) to refer to it within a program.
-
For the C API, these constants are capitalized and start with
CPX_PARAM_; for example, CPX_PARAM_ITLIM. They are used as the second argument in all parameter routines (except CPXsetdefaults which does not require them).
-
For C++ applications, the parameters are defined in nested enumeration types for Boolean, integer, floating-point, and string parameters. The
enum names use mixed (lower and upper) case letters and must be prefixed with the class name IloCplex:: for scope. For example, IloCplex::ItLim is the IloCplex equivalent of CPX_PARAM_ITLIM.
-
For Java applications, the parameters are defined as final static objects in nested classes called
IloCplex.BooleanParam, IloCplex.IntParam, IloCplex.DoubleParam, and IloCplex.StringParam for Boolean, integer, floating-point, and string parameters, respectively. The parameter object names use mixed (lower and upper) case letters and must be prefixed with the appropriate class for scope. For example, IloCplex.IntParam.ItLim is the object representing the parameter CPX_PARAM_ITLIM.
-
For .NET applications, the parameters follow the usual conventions for capitalizing attributes and defining scope within a namespace.
An integer that serves as a reference number for each parameter is shown in the table. That integer reference number corresponds to the value that each symbolic constant represents, as found in the cplex.h header file, but it is strongly recommended that the symbolic constants be used instead of their integer equivalents whenever possible, for the sake of portability to future versions of CPLEX.
PREVIOUS
NEXT