25.11.2015 Views

The MOSEK command line tool Version 7.0 (Revision 141)

The MOSEK command line tool. Version 7.0 ... - Documentation

The MOSEK command line tool. Version 7.0 ... - Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

46 CHAPTER 5. THE OPTIMIZERS FOR CONTINUOUS PROBLEMS<br />

Parameter name<br />

MSK DPAR INTPNT NL TOL PFEAS<br />

MSK DPAR INTPNT NL TOL DFEAS<br />

MSK DPAR INTPNT NL TOL REL GAP<br />

MSK DPAR INTPNT TOL INFEAS<br />

MSK DPAR INTPNT NL TOL MU RED<br />

Purpose<br />

Controls primal feasibility<br />

Controls dual feasibility<br />

Controls relative gap<br />

Controls when the problem is declared infeasible<br />

Controls when the complementarity is reduced enough<br />

Table 5.3: Parameters employed in termination criteria.<br />

In this case the bounds<br />

f(x) = 1 x + 1<br />

1 − x . (5.6)<br />

0 ≤ x ≤ 1<br />

will not guarantee that <strong>MOSEK</strong> only evaluates the function for x between 0 and 1 . To force <strong>MOSEK</strong> to<br />

strictly satisfy both bounds on ranged variables set the parameter MSK IPAR INTPNT STARTING POINT<br />

to MSK STARTING POINT SATISFY BOUNDS.<br />

For efficiency reasons it may be better to reformulate the problem than to force <strong>MOSEK</strong> to observe<br />

ranged bounds strictly. For instance, (5.6) can be reformulated as follows<br />

f(x) = 1 x + 1 y<br />

0 = 1 − x − y<br />

0 ≤ x<br />

0 ≤ y.<br />

5.5.1.3 Interior-point termination criteria<br />

<strong>The</strong> parameters controlling when the general convex interior-point optimizer terminates are shown in<br />

Table 5.3.<br />

5.6 Solving problems in parallel<br />

If a computer has multiple CPUs, or has a CPU with multiple cores, it is possible for <strong>MOSEK</strong> to take<br />

advantage of this to speed up solution times.<br />

5.6.1 Thread safety<br />

<strong>The</strong> <strong>MOSEK</strong> API is thread-safe provided that a task is only modified or accessed from one thread at<br />

any given time — accessing two separate tasks from two separate threads at the same time is safe.<br />

Sharing an environment between threads is safe.

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

Saved successfully!

Ooh no, something went wrong!