Practice: Degenerate Basic Feasible Solutions
Question
Recognition · Classification
A system has
2 hints available, least help first.
Hint 1: Retrieval cue
How many positive components does a nondegenerate basic feasible solution have?
Hint 2: Concept cue
If only two are positive but the basis holds three variables, what is the third doing?
Direct application · Classification · Explanation
For the system
consider
(a) Verify it is a basic feasible solution. (b) Decide whether it is degenerate. (c) List every basis describing it. (d) Give the active-set reading.
Write your answer, then compare it with the worked solution.
2 hints available, least help first.
Hint 1: Retrieval cue
Count the strictly positive components and compare with
Hint 2: Strategy cue
For (c), ask which columns are forced into the basis and which are free to complete it.
Compare with the worked solution
Comparing does not record a result. Judging your own written answer cannot show that you can do this without help.
The columns are
(a) Feasible, and basic.
(b) Degenerate. One strictly positive component against
(c) The bases. Only
: , determinant . Solving gives , . : identical structure since . Gives , . : , determinant . Gives , .
Three bases, one point. In each the second basic variable sits at zero, which is the definition being met.
(d) Active sets. Both structural equalities are active, as always. Three nonnegativity restrictions are active,
A complete answer does each of these:
- detects from components
- geometric reading
- multiple bases
- algorithmic consequence
Comparison · Method selection
Two distinct corners of a feasible region attain the same optimal objective value. What does this indicate?
2 hints available, least help first.
Hint 1: Retrieval cue
How many distinct points are involved in each of the two phenomena?
Hint 2: Concept cue
Would changing the objective alter which corners are degenerate?
Interpretation
At a degenerate basic feasible solution, one or more basic variables equal zero.
Select every statement that holds at such a point.
Error diagnosis · Explanation · Evaluation
A student writes:
Each corner of the feasible region corresponds to one basis, so the number of iterations the simplex method takes equals the number of corners it visits. If the log shows twelve iterations, it visited twelve distinct corners and the objective improved twelve times.
Identify the error and say what the log might actually show.
Write your answer, then compare it with the worked solution.
2 hints available, least help first.
Hint 1: Retrieval cue
Is the map from bases to corners injective?
Hint 2: Concept cue
What happens to the point when a swap occurs at a corner with a basic variable already at zero?
Compare with the worked solution
Comparing does not record a result. Judging your own written answer cannot show that you can do this without help.
The error. The correspondence between extreme points and bases is not one-to-one. Every basic feasible solution is an extreme point, and every extreme point arises from at least one basis, but a degenerate corner, one with fewer than
Why that breaks both predictions. At a degenerate corner a basis swap can exchange one active constraint for another and land on the same point. The basis is new, the point is not, the step length is zero, and the objective is unchanged. So twelve iterations may have visited fewer than twelve corners, and the objective need not have improved at every step.
A concrete case. For
What the log might show. The same variable values at consecutive iterations with different basis index sets, and an objective column that does not change. That is stalling.
What it does not mean. Not a bug, and not an invalid answer. Occasional stalling is ordinary. The pathological case is cycling, where a sequence of zero-length steps returns to a basis already visited and repeats indefinitely; it is rare and is prevented by an anti-cycling rule such as Bland's, which selects entering and leaving variables by smallest index.
The correct general statement. Iterations bound corner visits from above, never below, and the objective is non-increasing for a minimisation rather than strictly decreasing.
A complete answer does each of these:
- detects from components
- geometric reading
- multiple bases
- algorithmic consequence
Transfer · Interpretation · Evaluation
Midway through a solve, an iteration's minimum ratio test produces the ratios
Say what you can predict about the next basic feasible solution before computing it, what will happen to the objective at the iteration after that if the entering variable's direction has a positive component in the tied row, and what a practitioner should watch for if this recurs.
Write your answer, then compare it with the worked solution.
2 hints available, least help first.
Hint 1: Retrieval cue
Two variables reach zero together, but only one can leave. What happens to the other?
Hint 2: Strategy cue
Work out the ratio in a row whose basic variable is already zero.
Compare with the worked solution
Comparing does not record a result. Judging your own written answer cannot show that you can do this without help.
What the tie predicts. Two basic variables reach zero at the same step length
Which leaves. Either tied row may be chosen. Both choices are valid and both lead to the same point; they differ only in which basis describes it, and the two resulting bases are among the several that name that corner.
The iteration after that. If the next entering variable has a positive direction component in the row whose basic variable sits at zero, that row's ratio is
What to watch for on recurrence. Repeated zero-length steps are not in themselves an error, and usually the method escapes after one or two. The concern is cycling: a sequence of such steps returning to a basis already visited, which repeats forever and never terminates. The symptom in a log is the same variable values recurring across many iterations with the basis index set changing and the objective column flat.
The remedy. An anti-cycling rule, most simply Bland's: choose the entering variable with the smallest index among those with negative reduced cost, and break leaving ties by smallest index. This guarantees termination. The cost is that entering variables are chosen by index rather than by steepest improvement, so the method usually takes more iterations. A guarantee obtained at the cost of average-case speed.
Why this is the transfer. The definition of degeneracy is a count of positive components, met statically. Here it arrives as a tie in an arithmetic test, several steps before the count could be taken, and recognising it there is what makes the subsequent zero step legible rather than alarming.
A complete answer does each of these:
- detects from components
- geometric reading
- multiple bases
- algorithmic consequence
Session complete
Every question in this set has been through once. What you can do now depends on how it went — practising again is worth more than moving on if any of it was uncertain.
Practice data
Your practice record is stored in this browser only. Clearing it removes every answer and every scheduled review, and cannot be undone.