The MOSEK command line tool Version 7.0 (Revision 141)

15.2. THE FILE FORMAT 301
– ‘NEAR DUAL INFEAS CER’,
– ‘NEAR INTEGER OPTIMAL’.
Most of these values are irrelevant for input solutions; when constructing a solution for simplex
hot-start or an initial solution for a mixed integer problem the safe setting is UNKNOWN.
A [solution]-section contains [con] and [var] sections. Each [con] and [var] section defines
solution information for a single variable or constraint, specified as list of KEYWORD/value pairs,
in any order, written as
KEYWORD=value
Allowed keywords are as follows:
– sk. The status of the item, where the value is one of the following strings:
∗ LOW, the item is on its lower bound.
∗ UPR, the item is on its upper bound.
∗ FIX, it is a fixed item.
∗ BAS, the item is in the basis.
∗ SUPBAS, the item is super basic.
∗ 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.