6.5.7 · D5Research Frontiers & Practice

Question bank — Continual and lifelong learning

1,715 words8 min readBack to topic

Before we start, one shared vocabulary reminder so no symbol appears unexplained:

Definition Quick symbol refresher (expand if rusty)
  • = the model's weights (all the tunable numbers).
  • = the loss (error score) on task ; smaller is better.
  • = the gradient, the arrow pointing in the direction that increases fastest; we step opposite to it.
  • = Fisher information of weight : how much predictions wobble when you nudge that one weight. Big = important weight.
  • = backward transfer: change in accuracy on old task caused by later training. Negative = forgetting.

True or false — justify

Catastrophic forgetting is caused by the model running out of storage space (parameters).
False. A network with millions of spare parameters still forgets; the cause is that plain SGD reuses the same shared weights and its gradient only knows the current task, so it happily overwrites old configurations. It is an optimisation problem, not a capacity one.
If the gradient for task 2 happened to be orthogonal to task 1's loss surface, no forgetting would occur.
True (locally). If moves only in directions where is flat, task 1's loss barely changes. Forgetting comes precisely from the overlap between the directions each task cares about.
A model that reaches a perfect minimum on task 1 () is safe from forgetting.
False. A zero gradient means task 2's update starts from , but the very first step can move straight uphill on . Being at a minimum protects you against nothing once you optimise a different objective.
Elastic Weight Consolidation (EWC) needs the old task's data at training time for task .
False. EWC stores only and the Fisher values — a summary. It never revisits , which is exactly why it is used when old data must be deleted (privacy, storage).
Experience replay needs to store the old data, so it fails whenever privacy forbids keeping raw examples.
Partly false. Plain replay does need raw data, but generative replay sidesteps this: you train a generator on old tasks and sample synthetic "pseudo-examples", storing no real records.
Progressive Neural Networks have exactly zero forgetting.
True by construction. Old columns' parameters are frozen and never updated when a new column is added, so no old prediction can drift. The price is that the model grows with every task.
A larger regularisation strength in EWC always improves overall performance.
False. Large buys stability but kills plasticity — the model becomes so rigid it can barely learn the new task. It is a trade-off dial, not a "bigger is better" knob.
Backward transfer (BWT) can be positive.
True. If learning a later task actually improves an old task (shared useful features), , giving positive BWT — the good case that meta-learning and shared representations aim for.
Reservoir sampling gives recent tasks a larger share of the memory buffer.
False. Reservoir sampling makes every example seen so far equally likely to be in the buffer (), regardless of arrival time — so early and late tasks are represented in proportion to how many examples they had, not recency.

Spot the error

"To measure forgetting on task , I subtract its initial accuracy from its final accuracy."
Error: you must compare against the task's peak accuracy (the over all checkpoints since learning it), not the initial. A task may keep improving for a while before decaying; measuring from initial hides that early gain and understates forgetting.
"Fisher information tells us which weights are large, so we protect the biggest weights."
Error: measures sensitivity of predictions to weight , not the weight's magnitude. A small weight can be highly important (big ) and a large weight can be irrelevant. Protecting by magnitude is a different, worse heuristic.
"The EWC penalty approximates the old loss using its gradient at ."
Error: it approximates the old loss with a second-order (quadratic/Hessian) Taylor term. The first-order gradient term is dropped because at the minimum; the curvature (Fisher ≈ Hessian diagonal) is what remains.
"In experience replay we add the new-task loss and old-buffer loss, so we take only the buffer gradient when it disagrees with the new task."
Error: both gradients are summed (weighted by ) and the update follows their combination. There is no "winner takes all" — the compromise direction is precisely what enforces stability.
"Class-balanced buffers and reservoir sampling do the same thing."
Error: reservoir sampling balances by arrival probability (proportional to task size); class-balanced buffers force equal examples per class. When tasks have skewed class counts these give very different memories, and class-balancing protects rare classes better.
"Lateral connections in Progressive Nets let new columns update old features to be more useful."
Error: old features are frozen; the lateral weights only learn how to read and reuse them for the new task. The old features themselves never change.

Why questions

Why does standard SGD forget but the human brain (mostly) does not?
SGD optimises only the current objective with one shared parameter set and no memory of the old loss. Brains use mechanisms like memory consolidation and separate/complementary systems (fast hippocampus, slow cortex) that rehearse and protect old traces — analogous to replay plus regularisation combined.
Why do we use the Fisher information rather than just the raw Hessian in EWC?
The full Hessian is huge and expensive, and can have negative eigenvalues (not a valid rigidity measure). The Fisher is a positive, cheap-to-estimate approximation of the Hessian diagonal that only needs first derivatives of the log-likelihood, giving a clean per-weight importance score.
Why does replay force a "compromise" solution rather than just satisfying the new task?
Because the summed loss injects old gradients back into every update. To lower the total loss, must find a point that is decent for both old and new tasks simultaneously — a compromise no single-task gradient would choose.
Why is the stability–plasticity dilemma a genuine dilemma and not just an engineering nuisance?
The two demands pull the same shared weights in opposite ways: staying put preserves old tasks (stability) but blocks learning new ones (plasticity). With one parameter set you cannot maximise both freely, so every method is really a choice of where on this spectrum to sit.
Why might generative replay quietly degrade over many tasks?
The generator is itself a continually-learned model, so it forgets old distributions too. Sampling from a decayed generator produces lower-quality pseudo-examples, and errors compound task after task — a "forgetting of the forgetting-preventer".
Why can distillation help continual learning?
You can distil the old model's outputs on new (or buffered) inputs as soft targets, penalising the new model for drifting away from old predictions — a data-driven way to preserve old behaviour without keeping old labels.

Edge cases

What happens to EWC when the very first task's Fisher values are all essentially zero?
The penalty term vanishes, so EWC reduces to plain SGD and offers no protection — you get full forgetting. This signals that task 1's predictions were insensitive to all weights, i.e. it was near-trivial for the network.
What if two consecutive tasks are identical?
There is nothing to forget — old and new gradients align, EWC's penalty is automatically satisfied at , and replay just re-shows the same distribution. This is the degenerate "positive transfer, zero conflict" corner of the problem.
With a buffer of size and a data stream of length , what fraction of any single old example survives?
The keep-probability , so any specific old example almost surely gets evicted eventually. Replay's guarantee is statistical coverage of the distribution, never permanence of individual points.
In Progressive Nets, what is the cost of the "zero forgetting" guarantee as the number of tasks grows large?
Parameters and lateral connections grow (roughly quadratically in for the laterals), so memory and compute blow up. Zero forgetting is bought with unbounded model growth — fine for a handful of tasks, impractical for thousands.
What happens if in EWC?
The weights are frozen essentially completely at ; plasticity drops to zero and the model cannot learn the new task at all. This is the extreme-stability endpoint of the dilemma.
What happens if the replay weight ?
The old-buffer term disappears and the objective collapses back to pure new-task training — replay in name only, with forgetting returning to the plain-SGD level. is the stability dial for replay just as is for EWC.
If task boundaries are unknown (a smooth data stream with no "new task" signal), which methods still apply?
Replay-style and online methods still work because they never needed a boundary — you just keep sampling from the buffer. Boundary-triggered methods like classic EWC (which snapshots and computes Fisher at each task end) need adaptation, since there is no clear moment to snapshot.
Recall One-line self-test

Name the three solution families and their one-word mechanism. ::: Regularisation = protect important weights; Replay = rehearse old data; Architecture = isolate per-task parameters.