7.6 Retrieving information items

After the optimization the user has access to the solution as well as to a report containing a large amount of additional information items. For example, one can obtain information about:

• timing: total optimization time, time spent in various optimizer subroutines, number of iterations, etc.

• solution quality: feasibility measures, solution norms, constraint and bound violations, etc.

• problem structure: counts of variables of different types, constraints, nonzeros, etc.

• integer optimizer: integrality gap, objective bound, number of cuts, etc.

and more. Information items are numerical values of integer, long integer or double type. The full list can be found in the API reference:

• Double

• Integer

• Long

Certain information items make sense, and are made available, also during the optimization process. They can be accessed from a callback function, see Sec. 7.7 (Progress and data callback) for details.

Remark

For efficiency reasons, not all information items are automatically computed after optimization. To force all information items to be updated use the parameter iparam.auto_update_sol_info.

Retrieving the values

Values of information items are fetched using one of the methods

• Task.getdouinf for a double information item,

• Task.getintinf for an integer information item,

• Task.getlintinf for a long integer information item.

Each information item is identified by a unique name. The example below reads two pieces of data from the solver: total optimization time and the number of interior-point iterations.

Listing 7.4 Information items example. Click here to download.

          double tm = task.getdouinf(mosek.dinfitem.optimizer_time);
          int  iter = task.getintinf(mosek.iinfitem.intpnt_iter);     
           
          Console.WriteLine("Time: " + tm);
          Console.WriteLine("Iterations: " + iter);