Skip to main content

SLOP8412Semester 2 / 2026Postgraduate

AdvancedFréchetInceptionDistance

FID decides what counts as progress in generative modelling. Change the sample size and the score moves; change the network and the ranking can reverse. A reported FID is a claim about a protocol, not a property of a model.

Inspect the benchmark
Reference and candidate Gaussian contours Separate panels on the same scale. R is centred at zero. A shifts 2.263 units along the all-ones direction. B stays centred and has standard deviation 1.049. Contours run from 0.5 to 3 standard deviations. R REFERENCE A MEAN SHIFT B WIDER SPREAD

Select a distribution to inspect its conditions.

Same-scale 2D projections along the mean-shift direction.
Contours: 0.5–3 standard deviations. Scores use all 2,048 dimensions.

Closed-form rankingB  4.88 < A  5.12
Reference conditions / d = 2048 / lower is better

Benchmark 00 / closed-form truth

A perfect score can miss the shape.

The candidates you start with never change; the measurement does. Each time the measurement is caught out, the bench gains a candidate built to show how.

R Reference
0.00baseline
A Location shift
5.12true FID
B Spread shift
4.88true FID
C Shape failure
0.00visibly wrong

The candidate the score cannot distinguish

FID 0.00.
Different distributions.

R has one peak. C has two. Their mean and covariance agree exactly, so FID assigns zero distance to distributions with different shapes.

R · ReferenceC · Bimodal mixture
Different shapes with identical first two moments R has one peak at zero. C has two peaks near minus and plus 0.9. Both have mean zero and variance one. Their fitted Gaussian densities coincide. −4−2024Feature coordinate e₁

Two peaks survive in C. The Gaussian reference has only one.

Mean · both
0
Covariance · both
I
Population FID
0.00

Exact densities along e₁. C mixes two Gaussians equally, with means ±0.9 and component variance 0.19 on this axis; the other 2,047 coordinates match R. Zero is the population score, not a guarantee for finite samples.

Open defectA lower number does not guarantee a better distribution.

Who it is for

Postgraduates who have trained or evaluated a generative model at least once, and have read a results table without asking what N was. Assumes comfort with multivariate Gaussians, matrix decompositions, and Python with NumPy.

Not for anyone who wants to learn to build generative models; this course never trains one. Not for anyone who needs the number to be fine.

What you will do

Build a bench in week 1: a reference distribution and two candidates, small enough to run on a laptop and simple enough that every score has a closed form. Re-score it every week with that week’s method. Reproduce a published number and account for the gap. Construct a candidate the score gets wrong. Propose a replacement and judge it by the same standard. Keep a log.

What you leave with

You can read a reported FID and say what it depends on: the number of samples, the network that made the features, the reference set and the seed. You can estimate how far a score at your N sits above its limit, and tell whether the gap between two models is larger than that. You can build a distribution the score gets wrong, and write a report that states the protocol beside the number. A results table that leaves the protocol out will read to you as unfinished, and that change is what the twelve weeks are for.

Twelve weeks

A zero score is the beginning of the audit. Build the measurement, expose what it misses, then decide what deserves to count as evidence.

Arc ACompute it

Establish what the number measures and reproduce it under controlled conditions.

  1. Week 013 August 2026

    The number

    The bold number in a results table is the field's account of what got better, and nothing in the table says what it was computed against. The bench is built here.

  2. Week 0210 August 2026

    The Fréchet distance

    The closed form for two Gaussians, derived rather than quoted, and the assumption it smuggles in

  3. Week 0317 August 2026

    The instrument

    Inception-v3 was trained to name a thousand ImageNet classes. The score measures distance in the space it built to do that.

  4. Week 0424 August 2026

    Getting it right

    The same samples can receive different scores. Separate preprocessing from numerical arithmetic, then pin the protocol you can defend.

Arc BBreak it

Test the assumptions: sample bias, missing shape, and what changes beyond images.

  1. Week 0531 August 2026

    The bias

    Finite-sample FID is biased, the bias depends on the generator, and fixing N does not repair the comparison

  2. Week 067 September 2026

    Blind spots

    A generator that memorised the reference set scores perfectly. What else the score cannot see, demonstrated on the bench.

  3. Week 0721 September 2026

    Dropping the Gaussian

    An unbiased estimator need not detect every difference. Compare KID, density and coverage against the bench's known Gaussian-distance baseline.

  4. Week 0828 September 2026

    Video

    FVD keeps the Gaussian distance but changes the features. Test what a temporal instrument preserves before transferring claims from images.

Arc CLive with it

Compare the score with human judgement and decide what evidence to report.

  1. Week 095 October 2026

    Human evaluation

    The judgement the score stands in for. How a rating study is designed, what it costs, and why it is so rarely run.

  2. Week 1012 October 2026

    Correlation

    Put the ranking a score produces beside the ranking people produce, and ask whether they agree. That question decides whether the previous nine weeks were worth doing.

  3. Week 1119 October 2026

    Why it persists

    Nine years of results tables carry an FID column, and that continuity is the strongest argument anyone has for keeping it. What the number costs to leave out, stated honestly.

  4. Week 1226 October 2026

    What you would report instead

    Defend your proposal by the standard built across the semester. Bring the final bench comparison and the conditions under which you would still report FID.

The bench

It starts as one reference set and two candidates, in the 2048 dimensions a feature extractor would have produced, chosen so that every score has a closed form and can be checked by hand. It does not stay that size. Every candidate after B arrives in the week the score is caught out.

R
N(0, I). The reference set.
A
N(0.05·1, I). Mean shifted, covariance untouched. FID 5.12.
B
N(0, 1.1·I). Mean exact, covariance too wide. FID 4.88.
C
Week 6. A bimodal mixture with R’s mean and R’s covariance. FID 0, and visibly wrong.
D
Week 6, and yours. Scores worse than A while looking closer to R, under a measure you write down before you look at the number.
E
Week 8, once the recordings have time in them. Every frame raised by the same amount.
F
Week 8. Every frame kept, their order destroyed. Two instruments disagree about whether E or F is the worse candidate.
Estimated FID for candidates A and B plotted against one over N. Every estimate sits far above its true value, and B is measured as further from R than A at every sample size, which reverses the true ordering.
B is closer to R than A is, and no sample size in this sweep says so.

Where to go next