7.3 Input/Output

7.3.1 Stream logging

By default the solver prints a log output analogous to the one produced by the command-line version of MOSEK. Logging may be turned off using the option verbose, for example:

r <- mosek(prob, list(verbose=0))

7.3.2 Log verbosity

The logging verbosity can be controlled by setting the relevant parameters, as for instance

Each parameter controls the output level of a specific functionality or algorithm. The main switch is MSK_IPAR_LOG which affect the whole output. The actual log level for a specific functionality is determined as the minimum between MSK_IPAR_LOG and the relevant parameter. For instance, the log level for the output produce by the interior-point algorithm is tuned by the MSK_IPAR_LOG_INTPNT; the actual log level is defined by the minimum between MSK_IPAR_LOG and MSK_IPAR_LOG_INTPNT.

Tuning the solver verbosity may require adjusting several parameters. It must be noticed that verbose logging is supposed to be of interest during debugging and tuning. When output is no more of interest, the user can easily disable it globally with MSK_IPAR_LOG. Larger values of MSK_IPAR_LOG do not necessarily result in increased output.

By default MOSEK will reduce the amount of log information after the first optimization on a given problem. To get full log output on subsequent re-optimizations set MSK_IPAR_LOG_CUT_SECOND_OPT to zero.

7.3.3 Saving a problem to a file

An optimization problem can be dumped to a file using the function mosek_write. The file format will be determined from the filename’s extension. Supported formats are listed in Sec. 14 (Supported File Formats) together with a table of problem types supported by each.

For instance the problem can be written to a human-readable PTF file with

r <- mosek_write(prob, "dump.ptf");

All formats can be compressed with gzip by appending the .gz extension, and with ZStandard by appending the .zst extension, for example

r <- mosek_write(prob, "dump.task.gz");

Some remarks:

  • The problem is written to the file as it is represented in the underlying optimizer task, that is including any auxiliary variables introduced by the R-to-C interface, if applicable.

  • Unnamed variables are given generic names. It is therefore recommended to use meaningful variable names if the problem file is meant to be human-readable.

  • The task format is MOSEK’s native file format which contains all the problem data as well as solver settings.

7.3.4 Reading a problem from a file

A problem saved in any of the supported file formats can be read directly into a problem structure using the function mosek_read. Afterwards the problem can be optimized, modified, etc.

r <- mosek_read("dump.ptf");
r$prob