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

F.3. THE OPF FORMAT 609
Note that a [solution]-section must be always specified inside a [solutions]-section. The
syntax of a [solution]-section is the following:
[solution SOLTYPE status=STATUS]...[/solution]
where SOLTYPE is one of the strings
– ‘interior’, a non-basic solution,
– ‘basic’, a basic solution,
– ‘integer’, an integer solution,
and STATUS is one of the strings
– ‘UNKNOWN’,
– ‘OPTIMAL’,
– ‘INTEGER OPTIMAL’,
– ‘PRIM FEAS’,
– ‘DUAL FEAS’,
– ‘PRIM AND DUAL FEAS’,
– ‘NEAR OPTIMAL’,
– ‘NEAR PRIM FEAS’,
– ‘NEAR DUAL FEAS’,
– ‘NEAR PRIM AND DUAL FEAS’,
– ‘PRIM INFEAS CER’,
– ‘DUAL INFEAS CER’,
– ‘NEAR PRIM INFEAS CER’,
– ‘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.