Worked examples — Orthogonal sets and orthonormal basis
The scenario matrix
Every problem in this topic is one of these cells. The examples below are labelled with the cell they cover. (Here is the flat sheet the basis spans, as just defined.)
| Cell | Situation | What's tricky | Example |
|---|---|---|---|
| C1 | Orthogonal (not unit) basis, inside | Must keep the denominator | A |
| C2 | Orthonormal basis | Denominator is — don't write it | B |
| C3 | Orthogonal set of size ; outside span | Formula gives a projection, not | C |
| C4 | Degenerate: a zero vector in the set | Independence breaks; length-squared divides by zero | D |
| C5 | Sign cases — negative coordinates, mixed-sign components | Bookkeeping of signs in dot products | E |
| C6 | Orthogonal matrix preserves length/angle | Verify ; check norm | F |
| C7 | Limiting case — near-orthogonal vectors, what "almost" costs | Small off-diagonal error | G |
| C8 | Word problem (signals / forces) mapped to coordinates | Translating words into dot products | H |
| C9 | Exam twist — "orthogonal columns" that are not orthonormal | Naming trap; must normalize first | I |
Example A — Cell C1: orthogonal basis, keep the denominator
Step 1 — check orthogonal. ✓ Why this step? Only then does the shortcut formula apply. (Here the generic of the parent note are our — same formula, matching names.)
Step 2 — the two dot products in the numerator. Why this step? The numerator measures "how much of points along ."
Step 3 — the denominators (the length-squared). Why this step? Because the are not unit vectors, we must divide out their own size. Skipping this is the classic error.
Step 4 — assemble.
Verify: ✓
Example B — Cell C2: orthonormal, no denominator
Step 1 — confirm unit length. ✓ Why this step? Once each , the coordinate is just .
Step 2 — dot products. Why this step? No denominator needed — orthonormality already did that division for us.
Verify: ✓ Same , different coordinates — consistent with A.
Example C — Cell C3: outside the span → projection

Step 1 — apply the formula anyway. Why this step? The formula never asked whether ; it just projects.
Step 2 — build the result. Why this step? This is the point of closest to — the Orthogonal projection onto the plane. The part is dropped because no basis vector points up.
Step 3 — the leftover is orthogonal to . Why this step? This is the defining property of a projection — the error is perpendicular to the subspace, the seed of Least squares.
Verify: (they differ in the third slot), and the residual dots to with both basis vectors. ✓ The lesson of C3: the formula always returns the projection; it only equals when actually lives in the span.
Example D — Cell C4: a zero vector poisons the set
Step 1 — is it "orthogonal"? . Technically yes — the zero vector is orthogonal to everything. Why this step? The definition only bans nonzero distinct pairs from being non-perpendicular; it says nothing about zero, so zero sneaks in.
Step 2 — independence fails. The relation holds with a nonzero coefficient. So the set is dependent — it is not a basis. Why this step? Section 2 of the parent required nonzero orthogonal vectors. The proof isolates ; when it cannot conclude .
Step 3 — the formula divides by zero. Why this step? The denominator is exactly the length-squared, which is only for the zero vector.
Verify: , confirming the division is illegal. ✓ Rule: always discard zero vectors before calling a set orthogonal.
Example E — Cell C5: all the signs
Step 1 — orthogonality (three checks). Why this step? Every pair must vanish or the shortcut is invalid.
Step 2 — numerators (watch the signs). Why this step? A zero numerator () is legal and meaningful — has no component along .
Step 3 — denominators, then divide. Why this step? The are orthogonal but not unit length, so we must divide each numerator by its own length-squared — otherwise the reconstructed vector would come out scaled wrong.
Verify: ✓ Sign bookkeeping survived intact.
Example F — Cell C6: rotation preserves length and angle

Step 1 — confirm orthonormal columns. Column 1 length; columns dot to . So (the clean -diagonal grid). Why this step? Length-preservation follows from , not from being "some" matrix — see QR decomposition where this -with-orthonormal-columns is the .
Step 2 — apply . Why this step? We rotate the vector units long by ; the figure shows the arc it sweeps.
Step 3 — compare norms. Why this step? This is the whole point of the example — putting the two lengths side by side is what confirms the geometric claim "rotation doesn't stretch," turning the abstract identity into a concrete number match.
Verify: and . ✓ Length untouched, exactly as Dot product and norms predicts for orthonormal maps.
Example G — Cell C7: the limiting / "almost orthogonal" case
Step 1 — the true off-diagonal. . Why this step? This nonzero entry is exactly what the shortcut assumes is zero; it is the source of all error.
Step 2 — naive coordinates. Why this step? This is what a careless solver writes, ignoring the non-orthogonality.
Step 3 — reconstruct and measure error. Error vector . Why this step? It quantifies the cost of pretending "almost orthogonal" equals "orthogonal."
Verify: with , the first error component and second . Both as . ✓ Moral: near-orthogonality is not orthogonality — for exactness, run Gram-Schmidt process first.
Example H — Cell C8: word problem (two microphones)
Step 1 — confirm orthonormal. ; . ✓ Why this step? Only orthonormal channels let each reading be a single dot product with no crosstalk.
Step 2 — channel readings = dot products. Why this step? Each channel measures the component of along its own direction.
Step 3 — energy check (Parseval). Why this step? Orthonormal bases conserve total energy — a physical sanity check the engineer relies on.
Verify: , and ✓
Example I — Cell C9: the exam naming trap
Step 1 — columns orthogonal? ✓ Perpendicular, yes. Why this step? The claim's premise is genuinely true — that's what makes the trap seductive.
Step 2 — but are they unit vectors? Each column has length. Why this step? "Orthogonal matrix" (a historical misnomer) demands orthonormal columns. Length matters, so we must test it.
Step 3 — test . Why this step? An orthogonal matrix must satisfy (the clean -diagonal grid); here we get instead, which shows . In fact .
Step 4 — the fix: normalize. Divide every column by its length . Then has orthonormal columns, and now . Why this step? Normalizing forces each column's length-squared to , which is precisely the missing condition, converting the merely-orthogonal into a true orthogonal matrix .
Verify: (so is not orthogonal), while . ✓ The word "orthogonal matrix" secretly means orthonormal + square — the same distinction that matters for Eigenvalues and eigenvectors of symmetric matrices.
Recall Which cell is this?
A basis has perpendicular columns but lengths . To get coordinates you... ::: keep the denominator (Cell C1 — orthogonal, not orthonormal). The coordinate formula runs fine but returns a vector . What happened? ::: was outside the span; you got its projection (Cell C3). Your denominator is . Diagnosis? ::: A zero vector is in the set — discard it (Cell C4). "Orthogonal columns ⇒ orthogonal matrix." True? ::: No — needs unit length and square (Cell C9); normalize first.