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

Optimizer API for Python - Documentation - Mosek Optimizer API for Python - Documentation - Mosek

25.11.2015 Views

568 APPENDIX D. API CONSTANTS iinfitem.sol itg solsta Solution status of the integer solution. Updated after each optimization. iinfitem.sol itr prosta Problem status of the interior-point solution. Updated after each optimization. iinfitem.sol itr solsta Solution status of the interior-point solution. Updated after each optimization. iinfitem.sto num a cache flushes Number of times the cache of A elements is flushed. A large number implies that maxnumanz is too small as well as an inefficient usage of MOSEK. iinfitem.sto num a realloc Number of times the storage for storing A has been changed. A large value may indicates that memory fragmentation may occur. iinfitem.sto num a transposes Number of times the A matrix is transposed. A large number implies that maxnumanz is too small or an inefficient usage of MOSEK. This will occur in particular if the code alternate between accessing rows and columns of A. D.14 Information item types inftype.dou type Is a double information type. inftype.int type Is an integer. inftype.lint type Is a long integer. D.15 Hot-start type employed by the interior-point optimizers. intpnthotstart.none The interior-point optimizer performs a coldstart. intpnthotstart.primal The interior-point optimizer exploits the primal solution only.

D.16. INPUT/OUTPUT MODES 569 intpnthotstart.dual The interior-point optimizer exploits the dual solution only. intpnthotstart.primal dual The interior-point optimizer exploits both the primal and dual solution. D.16 Input/output modes iomode.read The file is read-only. iomode.write The file is write-only. If the file exists then it is truncated when it is opened. Otherwise it is created when it is opened. iomode.readwrite The file is to read and written. D.17 Language selection constants language.eng English language selection language.dan Danish language selection D.18 Long integer information items. liinfitem.bi clean dual deg iter Number of dual degenerate clean iterations performed in the basis identification. liinfitem.bi clean dual iter Number of dual clean iterations performed in the basis identification. liinfitem.bi clean primal deg iter Number of primal degenerate clean iterations performed in the basis identification. liinfitem.bi clean primal dual deg iter Number of primal-dual degenerate clean iterations performed in the basis identification.

568 APPENDIX D. <strong>API</strong> CONSTANTS<br />

iinfitem.sol itg solsta<br />

Solution status of the integer solution. Updated after each optimization.<br />

iinfitem.sol itr prosta<br />

Problem status of the interior-point solution. Updated after each optimization.<br />

iinfitem.sol itr solsta<br />

Solution status of the interior-point solution. Updated after each optimization.<br />

iinfitem.sto num a cache flushes<br />

Number of times the cache of A elements is flushed. A large number implies that maxnumanz is<br />

too small as well as an inefficient usage of <strong>MOSEK</strong>.<br />

iinfitem.sto num a realloc<br />

Number of times the storage for storing A has been changed. A large value may indicates that<br />

memory fragmentation may occur.<br />

iinfitem.sto num a transposes<br />

Number of times the A matrix is transposed. A large number implies that maxnumanz is too small<br />

or an inefficient usage of <strong>MOSEK</strong>. This will occur in particular if the code alternate between<br />

accessing rows and columns of A.<br />

D.14 Information item types<br />

inftype.dou type<br />

Is a double information type.<br />

inftype.int type<br />

Is an integer.<br />

inftype.lint type<br />

Is a long integer.<br />

D.15 Hot-start type employed by the interior-point <strong>optimizer</strong>s.<br />

intpnthotstart.none<br />

<strong>The</strong> interior-point <strong>optimizer</strong> performs a coldstart.<br />

intpnthotstart.primal<br />

<strong>The</strong> interior-point <strong>optimizer</strong> exploits the primal solution only.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!