6.8 Integer Optimization¶
An optimization problem where one or more of the variables are constrained to integer values is called a (mixed) integer optimization problem. MOSEK supports integer variables in combination with linear, quadratic and quadratically constrtained and conic problems (except semidefinite). See the previous tutorials for an introduction to how to model these types of problems.
6.8.1 Example MILO1¶
We use the example
to demonstrate how to set up and solve a problem with integer variables. It has the structure of a linear optimization problem except for integrality constraints on the variables. Therefore, only the specification of the integer constraints requires something new compared to the linear optimization problem discussed previously.
First, the integrality constraints are imposed using the function Task.putvartype or one of its bulk analogues:
for (int j = 0; j < numvar; ++j)
task.putvartype(j, mosek.variabletype.type_int);
Next, the example demonstrates how to set various useful parameters of the mixed-integer optimizer. See Sec. 13.4 (The Optimizer for Mixed-Integer Problems) for details.
/* Set max solution time */
task.putdouparam(mosek.dparam.mio_max_time, 60.0);
The complete source for the example is listed Listing 6.13. Please note that when we fetch the solution then the integer solution is requested by using soltype.itg. No dual solution is defined for integer optimization problems.
6.8.2 Specifying an initial solution¶
It is a common strategy to provide a starting feasible point (if one is known in advance) to the mixed-integer solver. This can in many cases reduce solution time.
There are two modes for MOSEK to utilize an initial solution.
A complete solution. MOSEK will first try to check if the current value of the primal variable solution is a feasible point. The solution can either come from a previous solver call or can be entered by the user, however the full solution with values for all variables (both integer and continuous) must be provided. This check is always performed and does not require any extra action from the user. The outcome of this process can be inspected via information items
iinfitem.mio_initial_feasible_solutionanddinfitem.mio_initial_feasible_solution_obj, and via theInitial feasible solution objectiveentry in the log.A partial integer solution. MOSEK can also try to construct a feasible solution by fixing integer variables to the values provided by the user (rounding if necessary) and optimizing over the remaining continuous variables. In this setup the user must provide initial values for all integer variables. This action is only performed if the parameter
iparam.mio_construct_solis switched on. The outcome of this process can be inspected via information itemsiinfitem.mio_construct_solutionanddinfitem.mio_construct_solution_obj, and via theConstruct solution objectiveentry in the log.
In the following example we focus on inputting a partial integer solution.
Solution values can be set using Task.putxx, Task.putxxslice or similar .
here to download.¶ // Assign values to integer variables.
// We only set a slice of xx
double[] values = {1.0, 1.0, 0.0};
task.putxxslice(mosek.soltype.itg, 0, 3, values);
// Request constructing the solution from integer variable values
task.putintparam(mosek.iparam.mio_construct_sol, mosek.onoffkey.on);
The log output from the optimizer will in this case indicate that the inputted values were used to construct an initial feasible solution:
Construct solution objective : 1.950000000000e+01
The same information can be obtained from the API:
int constr = task.getintinf(mosek.iinfitem.mio_construct_solution);
double constrVal = task.getdouinf(mosek.dinfitem.mio_construct_solution_obj);
Console.WriteLine("Construct solution utilization: " + constr);
Console.WriteLine("Construct solution objective: " + constrVal);
6.8.3 Example MICO1¶
Integer variables can also be used arbitrarily in conic problems (except semidefinite). We refer to the previous tutorials for how to set up a conic optimization problem. Here we present sample code that sets up a simple optimization problem:
The canonical conic formulation of (6.29) suitable for Optimizer API for .NET is
public class mico1
{
public static void Main ()
{
using (Task task = new Task())
{
// Directs the log task stream to the user specified
// method task_msg_obj.streamCB
MsgClass task_msg_obj = new MsgClass ();
task.set_Stream (mosek.streamtype.log, task_msg_obj);
task.appendvars(3); // x, y, t
int x=0, y=1, t=2;
task.putvarboundsliceconst(0, 3, mosek.boundkey.fr, -0.0, 0.0);
// Integrality constraints for x, y
task.putvartypelist(new int[]{x,y},
new mosek.variabletype[]{mosek.variabletype.type_int, mosek.variabletype.type_int});
// Set up the affine expressions
// x, x-3.8, y, t, 1.0
task.appendafes(5);
task.putafefentrylist(new long[]{0,1,2,3},
new int[]{x,x,y,t},
new double[]{1,1,1,1});
task.putafegslice(0, 5, new double[]{0, -3.8, 0, 0, 1.0});
// Add constraint (x-3.8, 1, y) \in \EXP
task.appendacc(task.appendprimalexpconedomain(), new long[]{1, 4, 2}, null);
// Add constraint (t, x, y) \in \QUAD
task.appendacc(task.appendquadraticconedomain(3), new long[]{3, 0, 2}, null);
// Objective
task.putobjsense(mosek.objsense.minimize);
task.putcj(t, 1);
// Optimize the task
task.optimize();
task.solutionsummary(mosek.streamtype.msg);
double[] xx = task.getxxslice(mosek.soltype.itg, 0, 2);
Console.WriteLine ("x = {0}, y = {1}", xx[0], xx[1]);
}
}
}
}
Error and solution status handling were omitted for readability.
