Gradient Descent Revisited — Slow Plateaus and Contour Maps
On this page 6 headings
Watch a gradient step reduce a loss
Use the one-parameter bowl L(w) = ½w², starting at w = 2, with learning rate 0.25.
Compute the current loss and gradient.
Move opposite to the gradient.
Evaluate the new point.
What changed? The gradient points uphill; subtracting a suitable step moves downhill. A lower gradient near the minimum also makes steps smaller.
Quick check: At w = 0, what update does this rule make?
No change: the gradient is zero.
Swipe long formulas, tables or code sideways to see the rest.
Start here Week 2 gave us gradient descent. This week asks: is it fast? The answer: not always. On flat regions of the error surface it crawls. Before we fix that with better optimisers, we learn a simple tool to see what an optimiser is doing — the contour map.
- Sigmoid neuron , data (0.5, 0.2) and (2.5, 0.9).
- Loss . Guessing (w, b) by hand works for 2 parameters but not for millions.
- From the Taylor series: the loss falls fastest when we move opposite to the gradient.
- Update rule:
- For the sigmoid neuron: .
Full derivations are on the Week 2 page Gradient Descent.
The gradient is the slope Δy/Δx of the loss curve.
- Where the curve is steep, the gradient is large.
- Where the curve is gentle, the gradient is small.
Our update is . So:
- On steep parts → big steps.
- On gentle parts → tiny steps.
Lecture example — starting points Run gradient descent for steps from , and again from (−3, 2). Whatever the starting point, once the path reaches a gentle region, progress slows down a lot. Starting from (−4, −4) is even worse — the loss there is almost flat.
Everyday example Rolling a marble on a nearly flat table: it barely moves, even though the floor (the minimum) is somewhere ahead.
3D plots are hard to read. A contour map is a 2D way to show the same surface.
How it’s made: take horizontal slices of the error surface at equal heights (equal loss values). Look from the top. Each slice becomes a closed line — a contour. Every point on one contour has the same loss.
How to read a contour map:
| What you see | What it means |
|---|---|
| Contours close together | steep slope in that direction |
| Contours far apart | gentle slope |
| Innermost small ring | the minimum (lowest loss) |
This is exactly like height lines on a trekking map of a hill.
Gradient descent on a contour map: the path always crosses contours at right angles (the gradient is perpendicular to the contour line). Where contours are far apart, the dots of the path bunch together — tiny steps.
Plain gradient descent:
- takes a lot of time to cross regions with a gentle slope,
- because the gradient there is very small.
Can we do better? Yes — momentum-based gradient descent (next page).
One more thing to keep in mind: every optimiser starts by computing at the starting point.
In one line: Gradient descent moves fast on steep slopes and crawls on gentle ones; contour maps show the error surface from the top, where close lines mean steep and far lines mean gentle.
Exam words: gentle slope, steep slope, plateau, contour, contour map, equal-loss line, top view.
