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

610 APPENDIX F. MOSEK FILE FORMATS
∗ UNK, the status is unknown.
∗ INF, the item is outside its bounds (infeasible).
– lvl Defines the level of the item.
– sl Defines the level of the dual variable associated with its lower bound.
– su Defines the level of the dual variable associated with its upper bound.
– sn Defines the level of the variable associated with its cone.
– y Defines the level of the corresponding dual variable (for constraints only).
A [var] section should always contain the items sk, lvl, sl and su. Items sl and su are not
required for integer solutions.
A [con] section should always contain sk, lvl, sl, su and y.
An example of a solution section
[solution basic status=UNKNOWN]
[var x0] sk=LOW lvl=5.0 [/var]
[var x1] sk=UPR lvl=10.0 [/var]
[var x2] sk=SUPBAS lvl=2.0 sl=1.5 su=0.0 [/var]
[con c0] sk=LOW
[con c0] sk=UPR
[/solution]
lvl=3.0 y=0.0 [/con]
lvl=0.0 y=5.0 [/con]
• [vendor] This contains solver/vendor specific data. It accepts one argument, which is a vendor
ID – for MOSEK the ID is simply mosek – and the section contains the subsection parameters
defining solver parameters. When reading a vendor section, any unknown vendor can be safely
ignored. This is described later.
Comments using the ‘#’ may appear anywhere in the file. Between the ‘#’ and the following line-break
any text may be written, including markup characters.
F.3.2.2
Numbers
Numbers, when used for parameter values or coefficients, are written in the usual way by the printf
function. That is, they may be prefixed by a sign (+ or -) and may contain an integer part, decimal
part and an exponent. The decimal point is always ‘.’ (a dot). Some examples are
1
1.0
.0
1.
1e10
1e+10
1e-10
Some invalid examples are
e10 # invalid, must contain either integer or decimal part
. # invalid
.e10 # invalid
More formally, the following standard regular expression describes numbers as used:
[+|-]?([0-9]+[.][0-9]*|[.][0-9]+)([eE][+|-]?[0-9]+)?