Minimum Variance Control
The course's last task, and its heaviest exam topic. Given an ARMAX plant, the controller that minimises the variance of the tracking error is a short formula built from one polynomial division — but it only exists if seven hypotheses hold, and half the marks in the archive are awarded for checking them, repairing the ones that fail, and knowing which failure cannot be repaired at all.
This is the chapter the exam is built around
Nineteen questions in the archive are graded against this chapter — 128 of the 396 recorded marks, and at least one question in every one of the 12 sittings. No other chapter in the course comes close. If you revise one thing, revise the checklist in §03 and the stability result in §08; between them they account for over half of these marks.
01 · Where the problem comes from
Discretization, sampling, and the zeros it invents
Everything in this course is written in discrete time, but the plants being controlled are physical and continuous. Something has to convert one into the other, and that conversion is not neutral: it moves the poles by a known rule, and it invents zeros that were never in the plant. Those invented zeros are what will break the central assumption of this chapter, which is why the story starts here.
The layout is always the same. A digital algorithm — control, prediction, monitoring — sits between two converters. The A/D samples the plant output; the D/A drives the plant input. Box the D/A, the continuous system, and the A/D together and what you have, from the input/output point of view, is a discrete-time system. The question is what its model is.
The A/D discretizes in time and in amplitude. Time discretization is the sampling interval — 10 ms, say, giving a sampling frequency Hz. Amplitude discretization is the number of available levels: a 10-bit converter has of them. Cost and quality track both. The D/A is called a holder, and in practice always a zero-order hold — its output is a staircase, constant between samples. Higher-order holds exist and are not used. If is small enough relative to the plant’s dynamics, the staircase is negligible and the plant sees what is effectively a continuous signal — which is the assumption every formula below rests on.
The state-space conversion
There are two honest routes to a discrete-time model. Either run an experiment and identify one directly from sampled data — which is chapters 2 and 3 of this course, and gets you a discrete model by construction — or start from a continuous white-box model and convert it. This section is the second route.
Note what does not change: and pass through untouched. Only the dynamics matrix and the input matrix are transformed, and both through the same matrix exponential. Under the zero-order hold assumption this is exact at the sampling instants — not an approximation.
Poles map cleanly
The eigenvalues follow the sampling transformation rule :
This is the reason the unit circle plays the role in discrete time that the left half-plane plays in continuous time. The open left half-plane maps onto the interior of the unit disc, the imaginary axis onto the unit circle itself, and onto . Continuous-time stability is preserved exactly.
Zeros do not — and new ones appear
Zeros do not obey $e^{s\Delta T}$
There is no transformation rule for zeros. Expecting them to move like poles is the single most common error on this topic, and it is listed as a misconception on the archived question. Poles obey the exponential map; zeros move unpredictably — and sampling manufactures new ones that had no continuous-time counterpart at all.
Count them. A strictly proper continuous transfer function of order with zeros () becomes, after discretization, a transfer function with poles and zeros. The arithmetic is unforgiving:
These are the hidden zeros, and the fact that matters for the rest of this chapter is that they are usually non-minimum-phase — they land outside the unit circle.
Why this section comes first
Minimum variance control requires the plant numerator to be minimum phase. Section 08 will show that this requirement is the closed-loop stability condition. And this section has just shown that a perfectly well-behaved continuous plant can acquire non-minimum-phase zeros purely by being sampled. A plant that was controllable in continuous time can become un-MVC-able for no reason other than the choice of . That is not a footnote; it is why generalised MVC exists.
Approximate conversions
When is inconvenient, replace the derivative by a finite difference:
is Euler forward, is Euler backward, and the widely used case is the midpoint — the bilinear or Tustin transform.
Choosing
This is described in the lectures as the most critical choice in the whole conversion. The vocabulary first:
| symbol | meaning |
|---|---|
| sampling interval, in seconds | |
| sampling frequency in Hz; in rad/s | |
| Nyquist frequency; |
The intuitive rule is “the bigger , the better”: as approaches the discrete approximation degrades against the true , so a higher buys a wider band over which the discrete model is faithful.
Faster sampling is not free — and the worst cost is numerical
Beyond the obvious (more expensive converters, more computation per second, more memory to buffer a given span of signal) there is a failure mode that catches people out. Continuous poles at, say, and with a very small map to and — both crowding towards , differing in the sixth decimal place. All the poles squeeze against , and implementing the algorithm then demands numerical precision you may not have. The failure is arithmetic, not dynamical, which is exactly why it surprises people.
The balanced compromise taught in the course:
Aliasing
The realistic scenario is that the clean signal is narrow-band but the measurement is not. Suppose carries content up to 2 kHz because of noise, while the signal you care about is far slower, and you would like kHz (so Hz). Sample it directly and the 2 kHz content folds down into your band, indistinguishable from real signal. There are two standard fixes:
Analog anti-alias, then sample
analog low-pass with a 500 Hz cutoff A/D at kHz. The filter must be analog: once aliasing has been committed by the converter, no amount of digital filtering can undo it.
Over-sample, filter digitally, decimate
A/D at kHz digital low-pass at 500 Hz under-sampling unit down to 1 kHz. No analog anti-alias hardware is needed — at the price of initial digital over-sampling.
One question, three marks — but it feeds everything after it
Discretization is examined directly once in the archive (04/09/2024, 3 marks), asking for the state-space equations and a discussion of how poles and zeros transform. The marks are small; the consequence is not, because the hidden-zero result is what §03’s minimum-phase assumption is protecting against.
02 · The plant
The ARMAX setup, and what “minimum variance” minimises
Control completes the list of tasks this course has been working through: model the system (chapter 1), estimate what you cannot measure (chapters 4–5), and now compute the input. The mathematical machinery is deliberately the same as for estimation — a predictor does the work here too.
is the plant’s pure delay, and is the noise model. and are written monic — as §03 will insist, that is not a coincidence but a requirement. If , then is genuinely the delay of the system; if there is a hidden delay lurking in , and §04 shows how to extract it.
Minimum phase, and why it will matter
What a non-minimum-phase system looks like
Step a minimum-phase system and the output rises monotonically to its final value. Step a non-minimum-phase system and it first moves in the opposite direction before turning round and climbing — the inverse-response signature. Physical examples given in the lectures: steer angle to roll rate on a bicycle or motorcycle, and flap deflection to pitch rate on an aircraft. Controlling such a plant is hard for an intuitive reason: the first thing the output tells you after a control action is a lie, and a controller that reacts to it takes exactly the wrong decision.
MVC cannot be applied to a non-minimum-phase plant. That is not a matter of degraded performance — §08 shows the closed loop is actively unstable. The escape route is generalised MVC, in §10.
The target and the cost
The goal of a control system is to follow a desired target — the trajectory of a robot, the speed a driver is asking for. Perfect tracking would mean . The optimal control problem is to find the input that minimises the variance of the tracking error:
It is a variance — hence the name — and the problem is stochastic only because the disturbance is. Two further assumptions concern the reference itself:
Uncorrelated with the noise
. In practice always true: the reference comes from a driver, a planner or a setpoint, none of which know anything about the plant’s disturbance.
No preview — the worst case
is taken as completely unpredictable, so the best available forecast is the trivial one, . This is the classical assumption when a human defines the reference in real time. A fully autonomous system whose planner does have a short preview of the desired trajectory is a strictly easier problem.
03 · The checklist
Every hypothesis MVC rests on
Seven conditions, each a one-line check. They look like bureaucratic hygiene on first reading. They are not: §08 proves that two of them are the closed-loop stability condition, stated in advance. Learn them as a list first and understand them as stability later.
Five sittings, 42 marks — and the papers ask for the recitation
“MVC assumptions and canonical form” is the single hottest topic in the course question bank: 5 questions worth 42 marks across 5 of the 12 sittings (15/07/2023, 08/01/2024, June 2024, September 2025, February 2026). The wording matters — several papers say “explicitly mention all MVC hypotheses and check if they are satisfied”. Marks are awarded for the enumeration itself, not only for the arithmetic that follows it. Write all seven down, every time, even the ones that are trivially satisfied.
① The delay is genuine
, with . If it fails, a delay is hiding inside — pull it out and increase (§04, step 1).
② $B(z)$ is minimum phase
All roots of strictly inside the unit circle. This is the one that cannot be repaired.
③ I — zero relative degree
and have the same degree.
③ II — coprime
and share no common factors.
③ III — monic
The highest-order coefficient of each is 1.
③ IV — roots inside
All roots of and of strictly inside the unit circle.
④ and ⑤ — the reference
, and no preview: . Technical assumptions; state them and move on.
Conditions ③ I–IV together are the statement that is in canonical representation — the same canonical form used for spectral factorisation elsewhere in the course.
Check on the $z$ form, not the $z^{-1}$ form
“Monic” and “roots strictly inside the unit circle” are statements about the polynomial in . A ratio like has to be rewritten as before you can read off a zero at and a pole at . Reading roots off the form is how acquires a phantom root at — a mistake recorded explicitly against the September 2025 paper, where the true root is , comfortably inside.
The checklist applied — the exam’s own format
Start from the difference equation
, with .
Collect the output terms and divide
, hence .
Read off the four objects
, , , .
Tick the list
① ✓ · ② has no roots at all, trivially minimum phase ✓ · ③ I both of degree 1 ✓ · ③ II no common factor ✓ · ③ III both monic ✓ · ③ IV zero at , pole at , both inside ✓. Assumptions satisfied — proceed to the predictor.
Know which polynomial each assumption constrains
and minimum phase are conditions on , the input path. Canonical representation is a condition on the pair , the noise path. Mixing them up makes an easy problem look unsolvable — and, in the other direction, makes an impossible problem look repairable. A bad root of is always fixable (§04). A bad root of is never fixable (§08).
04 · Making them true
The repair recipe, and the all-pass filter
Most exam systems fail the checklist as handed to you. That is the point of the question: the marks are in the repair, not in the verdict. There are three moves, they are applied in a fixed order, and each one changes something you must carry forward.
Four sittings, 28 marks
“All-pass repair” is examined in 4 questions worth 28 marks across 4 of the 12 sittings (29/01/2024, July 2024, February 2025, June 2026). The stem is always a variant of “are the assumptions satisfied? If not, and if it is possible, manipulate the model so that they are.” The phrase “if it is possible” is load-bearing — see §08 for the case where it is not.
① Delay the input until $b_0\ne0$ — this is what sets $k$
If the numerator carries a pure delay, factor it out into the term. Writing gives and leaves . Fixing and choosing are the same operation, not two.
② Factor out the scale factors and redefine the noise
Non-monic polynomials are repaired by pulling the constants out and absorbing them into a new white noise. The variance travels with them: with , so — the gain and the delay both move into .
③ Reflect bad roots of $C$ with an all-pass filter
A root of outside the unit circle is repaired, not approximated, by multiplying through by a unit-modulus factor that maps .
④ Re-normalise so both terms share one $A(z)$
After ② or ③ the two denominators frequently no longer match. The ARMAX form requires a single common ; skip this and , and the whole controller are wrong.
The all-pass filter
Because the modulus is exactly 1 at every frequency, multiplying a noise model by leaves the output spectrum unchanged:
Two filters with the same spectrum describe the same process, so nothing is lost — and the entire price of the repair appears in .
Why this is legitimate and not a fudge
The noise model is only ever a description of second-order statistics. Any two filters that produce the same spectrum describe the same stochastic process as far as this theory can see. The all-pass factor swaps a non-minimum-phase for a minimum-phase one with an identical spectrum — so the process is redefined, not approximated. Nothing is lost. This is the cleverest single idea in the chapter’s exercises, and it is why a bad root of is never fatal.
The system, and the diagnosis
, i.e. . Failures: ① ✗ · ③ I relative degree ✗ · ③ III not monic ✗ · ③ IV a zero at ✗. Only ② and ③ II pass.
Move ① — extract the delay
, so .
Moves ② — rescale to monic
with .
Move ③ — reflect the root at $z=-2$
With , multiply by . The numerator becomes and the noise becomes .
Move ④ — one common denominator
The input path still reads while the noise path reads . Rescaling the input path gives , and now
with every assumption satisfied.
Three ways this goes wrong
The reflection rescales the noise. multiplies the innovation by the reflected factor: , , in the archived papers. The scaling is absorbed into the redefined noise, never discarded — the controller is unchanged but the achievable output variance is not. A root of modulus exactly 1 is unfixable. Reflection maps to , so a root on the circle maps to itself; the June 2024 paper excludes that case rather than repairing it. Coprimality must be rechecked after the reflection, because the reflection moved a root of — which is why papers of this type exclude two values of the parameter, not one.
The all-pass repairs $C$, never $B$
Spectral equivalence is a statement about a stochastic process, so it is meaningful only on the noise path. carries deterministic input dynamics: reflecting a root of would change what the plant physically does, not merely how its noise is described. This is the reason a non-minimum-phase ends the discussion — and the reason §10 exists.
05 · The engine
The -step-ahead predictor
The controller is going to be built by demanding that the predicted output equal the reference. So everything hinges on one object — the -step-ahead predictor — and that object comes from a single polynomial long division.
Carry the division of by for exactly steps. The quotient is , of degree ; the remainder carries a factor , and is what is left after that factor is stripped off.
$\tilde R$ and $R$ differ by $z^{-k}$ — and only $\tilde R$ appears
This is the most frequently recorded slip on the whole topic. The identity defines ; the predictor and the control law use alone, with the delay already stripped. For that means , so if then , not . Getting this wrong shifts the entire controller by one step. A fast sanity check: , always.
The $k=1$ shortcut
When there is nothing to divide: and . Most archived instances are , so this shortcut covers most of them. It does not generalise — with the long division must genuinely be carried two steps, and using anyway is a recorded misconception on the 08/01/2024 paper.
One division, every predictor
The tableau after steps gives the -step predictor, so a single long division answers a question asking for several. For divided by :
| step | quotient | remainder | |
|---|---|---|---|
| 1 | |||
| 2 |
Why the horizon must equal the delay
A natural question is why the predictor’s horizon is locked to the plant’s delay . Shift the control law ahead by steps and it reads . If then and depends on future outputs — not causal, so it cannot be built. If then leans on older outputs than it needs — causal but suboptimal, throwing away information you already have. Only is both. The in every formula in this chapter is therefore forced, not chosen.
One question, eight marks
“-step predictor and MVC” appears once in the archive (16/07/2026, 8 marks) and asks for the 1-step and 2-step predictors before the controller — exactly the “one division, both answers” structure above. The same paper opens by demanding the assumption recitation from §03.
06 · Proof requested
Deriving the control law
This is the one place in the chapter where the marks are for the argument rather than the answer. The formula is three lines; the reason it is optimal is an orthogonality argument, and the papers ask for it by name.
The same stem in three sittings — and the proof is the marked content
“Find the general formula (proof is requested) of the optimal Minimum Variance controller for a generic ARMAX system.” This identical prompt appears in three sittings — 08/01/2024, 10/02/2025 and 16/07/2026 — and is deduplicated into a single 3-mark bank entry, which is why the topic table reads “1 question, 1 session” while the papers show three. Both numbers are correct; they count different things. The phrase “proof is requested” means the orthogonality step below is what earns the marks, not the boxed formula.
Deep dive The full derivation
The trick: split the output into predictor plus prediction error.
Substituting into the cost and expanding the square gives three terms:
Why the cross term vanishes — this is the proof. Carrying the division identity through gives , where has degree , so the error term involves only — noise that has not yet entered the system at time . It is therefore uncorrelated with everything measurable at , which covers the predictor (built from past data) and the reference (uncorrelated with by assumption ④). Predictor and prediction error are orthogonal by construction.
Two consequences follow immediately. The second term is irreducible — no controller can touch noise that has not arrived yet — and the minimisation collapses onto the first:
At time , however, is not available. Assumption ⑤ — no preview — says the best substitute is , giving the identity actually imposed: . Substituting the predictor and solving for finishes it.
Two routes to the same controller
Method I — apply the formula
Read , , , off the division and substitute. Fast, and the right choice under exam time pressure.
Method II — invert the predictor
Write the predictor, impose , shift by steps (legitimate precisely because assumption ⑤ says carries no preview), and solve for . Slower, but it shows why the controller is what it is: it drives the predicted output onto the reference.
Both give the same law. Learn Method II first and Method I becomes a shortcut rather than a memorised string. On the worked system of §03 — , , , , hence and — both routes land on
Sign and shape of the feedback term
The template subtracts . If is itself negative the term therefore enters with a plus — a control law printed as means , not . And the controller denominator is the product : divide out before reading , or you will mistake one for the other.
07 · What you get
The closed loop, and its four transfer functions
Close the loop with this controller and the result is startlingly simple — so simple that it is worth pausing over what has been hidden to achieve it.
The block scheme
Several papers ask you to draw this loop, so it is worth being able to reproduce it from memory. It splits into two halves, and every block in it has already appeared in this chapter.
The reference gets a pure delay; the noise gets — the remainder of the division, the part no controller can cancel.
The controller
enters through into a summing junction. The output is fed back through into the negative input of that same junction. The difference passes through , and what emerges is — which is the control law of §06, drawn instead of written.
The plant
passes through the delay and then through into a second summing junction. The noise reaches that junction through . The sum is , which closes the loop.
When the noise has a non-zero mean there is one extra arrow — see §09.
Reducing it
For a feedback loop with forward and feedback , the transfer function from input to output is : the direct path over one plus the loop function. Applying it here, the loop function collapses using the division identity :
Everything else follows in one line each:
None of them depends on the particular numbers. The first two carry the standard names: is the complementary sensitivity — how well follows — and is the sensitivity — how much the noise reaches the output. Their ideal values would be and respectively. Together they give the headline result of the chapter:
Against the ideal , exactly two things are lost, and both are irreducible. Tracking is perfect but steps late — the plant’s own delay, plus the fact that the reference cannot be previewed. And the noise cannot be driven to zero: the best achievable is , the prediction error itself.
Three sittings, 15 marks
“MVC closed-loop transfer functions” is examined in 3 questions worth 15 marks across 3 of the 12 sittings (September 2024, September 2025, June 2026). These questions usually hand you the plant and its controller and ask for one specific transfer function. The general results above are enough — one recorded misconception is doing the whole block-diagram algebra when already holds for any MVC meeting its assumptions.
The minimum variance itself
At steady state a constant reference satisfies , so the tracking error is , and its variance is a sum of squares because the noise terms are mutually uncorrelated:
For with that is . This number is the point of the whole chapter: it is the noise admitted during the steps the controller could not see. It grows with , because a longer delay means more unseen noise terms in — and it cannot be reduced by any controller whatsoever. Hence minimum variance.
A concrete check that MVC is a pure delay
Set the noise to zero and step the reference: for and for . With , , so , , , . The step arrives at the output exactly one sample late and is then perfectly on target forever. Noise-free MVC is a pure -step delay — nothing more, and nothing less.
What the simplicity is hiding
A closed loop whose behaviour is a pure delay plus a short moving average has almost no dynamics left in it. Those dynamics did not disappear — they became non-observable and non-controllable parts of the closed-loop system, in exactly the sense of the Kalman decomposition from chapter 1. That is precisely why §08 forbids cancelling when testing stability: the cancellation would hide modes that are still there, still evolving, and possibly still diverging.
08 · The capstone
— and when MVC destabilizes
Two sections of assumptions, one derivation, four transfer functions — and it all converges on a single product. The closed-loop characteristic polynomial of any minimum variance loop is , which means the hypotheses of §03 were never bureaucratic: they are the stability condition, written down in advance.
Two sittings, 12 marks — and both are the failing case
“MVC closed-loop stability” is examined in 2 questions worth 12 marks (July 2024 and February 2025). Both hand you a plant whose has a root outside the unit circle and ask you to discuss stability — the answer being that the loop is unstable and the MVC assumptions were never met. The trap in both is the invitation to cancel.
Recall the test. For a loop with forward and feedback , form the loop function and the characteristic polynomial — numerator plus denominator, with a minus for positive feedback. The loop is asymptotically stable if and only if every root of is strictly inside the unit circle.
Do not cancel $B(z)$ when forming $\chi$
appears in both the numerator and the denominator of , and cancelling it is the single most important procedural error in this chapter. A cancellation removes the mode from the expression while leaving it in the system — and if that mode is unstable, you have deleted the symptom rather than the instability. The July 2024 paper exists to catch exactly this, and says so explicitly. Note the asymmetry with §07: may be cancelled when computing a transfer function such as , because there you are describing an input–output map. It may not be cancelled when forming , because there you are enumerating the closed-loop modes.
The whole chapter in one line
Every root of is inside the unit circle by assumption ②. Every root of is inside by assumption ③ IV. So has all its roots inside, and a minimum variance loop is always asymptotically stable — provided the assumptions hold. The two conditions you were asked to check at the very beginning are not preconditions for the algebra to work; they are the closed-loop poles, named in advance. Learn this result and the checklist stops being a list to memorise.
When it fails, it fails loudly
If has a root outside the unit circle the controller is still computable — and actively harmful. Take a plant with , whose root sits at . The control law contains , and written as a difference equation that reads
The controller is inverting a non-minimum-phase numerator, and the inverse of a root outside the unit circle is an unstable pole placed inside the controller itself. The characteristic polynomial confirms it: keeps the root at no matter what the noise model does. In the February 2025 paper the root sits at and the controller’s is the recursion .
No parameter can save it, and the noise model is not to blame
A standard exam construction puts a free parameter in the noise polynomial and asks which values make MVC admissible. The answer is none — lives in , the offending root lives in , and §04 established that the all-pass repairs and never . Blaming the noise model when is perfectly canonical is a recorded misconception. The correct conclusion is narrow and important: MVC is always stabilising when its assumptions hold, and a non-minimum-phase is the one defect that cannot be repaired at all.
You form the loop function of an MVC design and notice that B(z) appears in both the numerator and the denominator. Under what circumstances may you cancel it?
09 · A common twist
Non-zero-mean noise and de-biasing
Every formula so far assumed . Two papers relax that to with , and the repair is a change of variable — applied, used, and then undone. Forgetting the last step is what the question is testing.
Two sittings, 17 marks
“De-biasing non-zero-mean noise” is examined in 2 questions worth 17 marks (September 2024 and July 2025). Both flag the non-zero mean explicitly in the stem — “note that the process has a non-zero mean” — so the twist is signposted rather than hidden. The marks are for handling it correctly to the end.
Repair the model first
Run the §04 recipe as usual. Note that the all-pass rescaling hits the mean as well as the variance: if and , then . Losing the mean here loses the whole question.
Find the output offset — the DC gain at $z=1$
A constant is a signal at , so evaluate the noise filter at . With noise path and mean , the offset is . It is the gain times the mean, not the mean.
Work in de-biased variables
Define (zero mean) and . In these variables the model is standard, so the ordinary predictor formula applies unchanged: .
Undo the change of variable — both branches
Substitute and . The two corrections partially cancel and leave an explicit constant behind:
The bias does not vanish — it reappears in the predictor
De-biasing is a change of variable used to reach the standard formula, not a way of making the mean go away. The final predictor carries an additive constant, and a student who drops it has a predictor that is systematically wrong by that constant forever. Note also that both branches must be un-substituted: the recorded misconception on the July 2025 paper is correcting the prediction but forgetting the feedback term, which is precisely what turns one constant into another.
In the closed-loop block diagram the correction shows up as a constant offset injected at the controller’s summing junction — a feed-forward term sitting outside the feedback path, which is a useful way to remember that it is a bookkeeping correction rather than part of the control law.
10 · The way out
Generalised MVC
Three limitations have accumulated. Generalised MVC answers all three with one change to the cost function. It is not examined in the archive, so this is a short section — but it is the answer to the question §08 leaves hanging.
MVC applies only to minimum-phase plants; it offers no way to moderate the control effort; and it lets you specify no behaviour at all between and — you get a pure delay, whether or not that is what you wanted.
and are design transfer functions, and setting , recovers plain MVC. They address the three limits in order. Putting the non-minimum-phase zeros of into lets GMVC handle plants MVC cannot touch. The term penalises control effort. And acts as a reference model, specifying the desired behaviour instead of accepting whatever falls out.
Optimal is not the same as desirable
Is — perfect tracking — always what you want? No. Consider cruise control with a staircase speed reference. With the car tracks each step as sharply as physics allows, which is optimal and deeply unpleasant to sit in. Choosing to be a low-pass filter makes the car ramp smoothly between speeds: worse by the tracking metric, better by the one that matters. The reference model is where you say what “good” means.
Minimum variance control — what to carry out of this chapter
- Discretization moves poles by and invents zeros, and those hidden zeros are usually non-minimum-phase. Sampling alone can make a well-behaved plant un-MVC-able.
- Seven assumptions: ; minimum phase; canonical (same degree, coprime, monic, roots inside); ; no preview. Check them on the form.
- The repair recipe: extract the delay to fix (this sets ), factor out scale factors into a redefined noise, reflect bad roots of with an all-pass, then re-normalise to one common . The rescaling carries the variance — and the mean.
- The all-pass repairs , never . Spectral equivalence is meaningful only on the noise path.
- One long division does everything: , with , and the tableau after steps is the -step predictor. Use , not . The horizon must equal the delay — smaller is non-causal, larger is suboptimal.
- The control law is , and the proof is the orthogonality of predictor and prediction error.
- The closed loop is , with , , , , and an irreducible variance .
- . Never cancel when forming it. A non-minimum-phase makes the MVC destabilize the plant, and no parameter in can rescue it — that is what GMVC is for.
Exam radar. This chapter carries 128 of the 396 recorded marks and appears in all 12 sittings. Before the exam, re-derive in this order: the seven-point checklist (§03 — 5 questions, 42 marks, and papers that ask you to recite it), the all-pass repair (§04 — 4 questions, 28 marks), the de-biasing un-substitution (§09 — 2 questions, 17 marks), the four closed-loop transfer functions (§07 — 3 questions, 15 marks) and with the cancellation trap (§08 — 2 questions, 12 marks). If you are short of time, §03 and §08 are the two that unlock the rest.