The MOSEK Python optimizer API manual Version 7.0 (Revision 141)

F.3. THE OPF FORMAT 611
F.3.2.3
Names
Variable names, constraint names and objective name may contain arbitrary characters, which in some
cases must be enclosed by quotes (single or double) that in turn must be preceded by a backslash.
Unquoted names must begin with a letter (a-z or A-Z) and contain only the following characters: the
letters a-z and A-Z, the digits 0-9, braces ({ and }) and underscore ( ).
Some examples of legal names:
an unquoted name
another name{123}
’single quoted name’
"double quoted name"
"name with \\"quote\\" in it"
"name with []s in it"
F.3.3
Parameters section
In the vendor section solver parameters are defined inside the parameters subsection. Each parameter
is written as
[p PARAMETER NAME] value [/p]
where PARAMETER NAME is replaced by a MOSEK parameter name, usually of the form MSK IPAR ...,
MSK DPAR ... or MSK SPAR ..., and the value is replaced by the value of that parameter; both integer
values and named values may be used. Some simple examples are:
[vendor mosek]
[parameters]
[p MSK IPAR OPF MAX TERMS PER LINE] 10 [/p]
[p MSK IPAR OPF WRITE PARAMETERS] MSK ON [/p]
[p MSK DPAR DATA TOL BOUND INF] 1.0e18 [/p]
[/parameters]
[/vendor]
F.3.4
Writing OPF files from MOSEK
The function Task.writedata can be used to produce an OPF file from a task.
To write an OPF file set the parameter iparam.write data format to dataformat.op as this ensures
that OPF format is used. Then modify the following parameters to define what the file should contain:
• iparam.opf write header, include a small header with comments.
• iparam.opf write hints, include hints about the size of the problem.
• iparam.opf write problem, include the problem itself — objective, constraints and bounds.
• iparam.opf write solutions, include solutions if they are defined. If this is off, no solutions
are included.
• iparam.opf write sol bas, include basic solution, if defined.