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
62 CHAPTER 7. THE ANALYZERS Supply Demand 200 Plant 1 1 2 Store 1 1100 1000 Plant 2 1 Store 2 200 5 Store 3 500 1000 Plant 3 2 1 2 Store 4 500 Figure 7.1: Supply, demand and cost of transportation. 7.2.1 Example: Primal infeasibility A problem is said to be primal infeasible if no solution exists that satisfy all the constraints of the problem. As an example of a primal infeasible problem consider the problem of minimizing the cost of transportation between a number of production plants and stores: Each plant produces a fixed number of goods, and each store has a fixed demand that must be met. Supply, demand and cost of transportation per unit are given in figure 7.1. The problem represented in figure 7.1 is infeasible, since the total demand exceeds the total supply 2300 = 1100 + 200 + 500 + 500 2200 = 200 + 1000 + 1000 If we denote the number of transported goods from plant i to store j by x ij , the problem can be formulated as the LP:
7.2. ANALYZING INFEASIBLE PROBLEMS 63 minimize x 11 + 2x 12 + 5x 23 + 2x 24 + x 31 + 2x 33 + x 34 subject to x 11 + x 12 ≤ 200, x 23 + x 24 ≤ 1000, x 31 + x 33 + x 34 ≤ 1000, x 11 + x 31 = 1100, x 12 = 200, x 23 + x 33 = 500, x 24 + x 34 = 500, x ij ≥ 0. (7.1) Solving the problem (7.1) using MOSEK will result in a solution, a solution status and a problem status. Among the log output from the execution of MOSEK on the above problem are the lines: Basic solution Problem status : PRIMAL INFEASIBLE Solution status : PRIMAL INFEASIBLE CER The first line indicates that the problem status is primal infeasible. The second line says that a certificate of the infeasibility was found. The certificate is returned in place of the solution to the problem. 7.2.2 Locating the cause of primal infeasibility Usually a primal infeasible problem status is caused by a mistake in formulating the problem and therefore the question arises: ”What is the cause of the infeasible status?” When trying to answer this question, it is often advantageous to follow these steps: • Remove the objective function. This does not change the infeasible status but simplifies the problem, eliminating any possibility of problems related to the objective function. • Consider whether your problem has some necessary conditions for feasibility and examine if these are satisfied, e.g. total supply should be greater than or equal to total demand. • Verify that coefficients and bounds are reasonably sized in your problem. If the problem is still primal infeasible, some of the constraints must be relaxed or removed completely. The MOSEK infeasibility report (Section 7.2.4) may assist you in finding the constraints causing the infeasibility. Possible ways of relaxing your problem include: • Increasing (decreasing) upper (lower) bounds on variables and constraints. • Removing suspected constraints from the problem. Returning to the transportation example, we discover that removing the fifth constraint x 12 = 200
- Page 27 and 28: Chapter 3 MOSEK and AMPL AMPL is a
- Page 29 and 30: 3.6. CONSTRAINT AND VARIABLE NAMES
- Page 31 and 32: 3.8. HOT-START 15 Linear dependency
- Page 33 and 34: 3.10. SENSITIVITY ANALYSIS 17 • .
- Page 35 and 36: Chapter 4 Problem formulation and s
- Page 37 and 38: 4.1. LINEAR OPTIMIZATION 21 be a pr
- Page 39 and 40: 4.2. CONIC QUADRATIC OPTIMIZATION 2
- Page 41 and 42: 4.2. CONIC QUADRATIC OPTIMIZATION 2
- Page 43 and 44: 4.3. SEMIDEFINITE OPTIMIZATION 27 4
- Page 45 and 46: 4.5. GENERAL CONVEX OPTIMIZATION 29
- Page 47 and 48: 4.5. GENERAL CONVEX OPTIMIZATION 31
- Page 49 and 50: Chapter 5 The optimizers for contin
- Page 51 and 52: 5.1. HOW AN OPTIMIZER WORKS 35 5.1.
- Page 53 and 54: 5.2. LINEAR OPTIMIZATION 37 5.2.2 T
- Page 55 and 56: 5.2. LINEAR OPTIMIZATION 39 Wheneve
- Page 57 and 58: 5.2. LINEAR OPTIMIZATION 41 5.2.2.3
- Page 59 and 60: 5.2. LINEAR OPTIMIZATION 43 • Rai
- Page 61 and 62: 5.5. NONLINEAR CONVEX OPTIMIZATION
- Page 63 and 64: 5.6. SOLVING PROBLEMS IN PARALLEL 4
- Page 65 and 66: Chapter 6 The optimizers for mixed-
- Page 67 and 68: 6.3. THE MIXED-INTEGER CONIC OPTIMI
- Page 69 and 70: 6.5. TERMINATION CRITERION 53 The f
- Page 71 and 72: 6.7. UNDERSTANDING SOLUTION QUALITY
- Page 73 and 74: Chapter 7 The analyzers 7.1 The pro
- Page 75 and 76: 7.1. THE PROBLEM ANALYZER 59 Constr
- Page 77: 7.2. ANALYZING INFEASIBLE PROBLEMS
- Page 81 and 82: 7.2. ANALYZING INFEASIBLE PROBLEMS
- Page 83 and 84: 7.2. ANALYZING INFEASIBLE PROBLEMS
- Page 85 and 86: 7.2. ANALYZING INFEASIBLE PROBLEMS
- Page 87 and 88: Chapter 8 Sensitivity analysis 8.1
- Page 89 and 90: 8.4. SENSITIVITY ANALYSIS FOR LINEA
- Page 91 and 92: 8.5. SENSITIVITY ANALYSIS WITH THE
- Page 93 and 94: 8.5. SENSITIVITY ANALYSIS WITH THE
- Page 95 and 96: Chapter 9 Parameters Parameters gro
- Page 97 and 98: 81 • MSK SPAR ITR SOL FILE NAME.
- Page 99 and 100: 83 • MSK DPAR INTPNT NL TOL REL G
- Page 101 and 102: 85 • MSK IPAR LOG MIO. Controls t
- Page 103 and 104: 87 • MSK DPAR INTPNT NL MERIT BAL
- Page 105 and 106: 89 • MSK IPAR INFEAS PREFER PRIMA
- Page 107 and 108: 91 • MSK IPAR SIM SAVE LU. Contro
- Page 109 and 110: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 111 and 112: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 113 and 114: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 115 and 116: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 117 and 118: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 119 and 120: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 121 and 122: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 123 and 124: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 125 and 126: 9.1. MSKDPARAME: DOUBLE PARAMETERS
- Page 127 and 128: 9.1. MSKDPARAME: DOUBLE PARAMETERS
7.2. ANALYZING INFEASIBLE PROBLEMS 63<br />
minimize x 11 + 2x 12 + 5x 23 + 2x 24 + x 31 + 2x 33 + x 34<br />
subject to x 11 + x 12 ≤ 200,<br />
x 23 + x 24 ≤ 1000,<br />
x 31 + x 33 + x 34 ≤ 1000,<br />
x 11 + x 31 = 1100,<br />
x 12 = 200,<br />
x 23 + x 33 = 500,<br />
x 24 + x 34 = 500,<br />
x ij ≥ 0.<br />
(7.1)<br />
Solving the problem (7.1) using <strong>MOSEK</strong> will result in a solution, a solution status and a problem<br />
status. Among the log output from the execution of <strong>MOSEK</strong> on the above problem are the <strong>line</strong>s:<br />
Basic solution<br />
Problem status : PRIMAL INFEASIBLE<br />
Solution status : PRIMAL INFEASIBLE CER<br />
<strong>The</strong> first <strong>line</strong> indicates that the problem status is primal infeasible. <strong>The</strong> second <strong>line</strong> says that a<br />
certificate of the infeasibility was found. <strong>The</strong> certificate is returned in place of the solution to the<br />
problem.<br />
7.2.2 Locating the cause of primal infeasibility<br />
Usually a primal infeasible problem status is caused by a mistake in formulating the problem and<br />
therefore the question arises: ”What is the cause of the infeasible status?” When trying to answer this<br />
question, it is often advantageous to follow these steps:<br />
• Remove the objective function. This does not change the infeasible status but simplifies the<br />
problem, eliminating any possibility of problems related to the objective function.<br />
• Consider whether your problem has some necessary conditions for feasibility and examine if these<br />
are satisfied, e.g. total supply should be greater than or equal to total demand.<br />
• Verify that coefficients and bounds are reasonably sized in your problem.<br />
If the problem is still primal infeasible, some of the constraints must be relaxed or removed completely.<br />
<strong>The</strong> <strong>MOSEK</strong> infeasibility report (Section 7.2.4) may assist you in finding the constraints causing the<br />
infeasibility.<br />
Possible ways of relaxing your problem include:<br />
• Increasing (decreasing) upper (lower) bounds on variables and constraints.<br />
• Removing suspected constraints from the problem.<br />
Returning to the transportation example, we discover that removing the fifth constraint<br />
x 12 = 200