Benchmarks and the Traps in Them · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

Scores that mislead honestly

Computing · Machine Learning · ages 22-24
Name ______________________   Date ____________
  1. Why judge models on held-out data?

    • Held-out data trains faster than the rest
    • Training data is too small to measure
    • The point is predicting cases never met before
  2. What is overfitting?

    • Fitting training data, including its noise, so new data fails
    • Using a model too simple to catch the pattern
    • Testing on data the model never saw
  3. A whole field tuning against one shared leaderboard can overfit the benchmark together.

    Circle one:   True   False

  4. A new method beats a baseline that its authors barely tuned. What is the honest next step?

    • Publish the win as proven progress
    • Tune the baseline as hard, then retest on fresh data
    • Tune the new method even harder instead
  5. A benchmark predates the pretraining corpus and scores look superb. What should you suspect?

    • Contamination: the test may sit inside the training text
    • Underfitting: the model is too simple for the test
    • Slow hardware: scores need faster chips
  6. Which list states what a benchmark win must assume to mean progress?

    • Separate test, equal tuning, fresh-data check
    • Bigger model, longer training, louder launch
    • Older test, weaker baseline, single metric
  7. A vendor reports one accuracy number with no tuning details and no fresh-data check. What do you reply?

    • Accept it, since arithmetic cannot mislead
    • Ask for the leak, tuning, and freshness guards before believing the claim
    • Ask for a bigger number on the same test
  8. A leaderboard climbs yearly while user complaints hold steady. What is the best diagnosis?

    • Users complain whatever the quality
    • The field overfits the shared test; the number rises, real skill stalls
    • Yearly climbs always equal real progress
LightMySky · lightmysky.comW1-mt_o9zLZbkaen-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

Scores that mislead honestly W1-mt_o9zLZbkaen-s1

  1. The point is predicting cases never met before · Only unseen cases test prediction instead of memory.
  2. Fitting training data, including its noise, so new data fails · Memorized training looks brilliant until fresh cases arrive.
  3. True · Shared reuse turns the field into one big tuner.
  4. Tune the baseline as hard, then retest on fresh data · Equal tuning plus fresh data splits real gains from artefacts.
  5. Contamination: the test may sit inside the training text · Seen exams flatter; the model may recite, not reason.
  6. Separate test, equal tuning, fresh-data check · Each guard blocks one of the three classic misleads.
  7. Ask for the leak, tuning, and freshness guards before believing the claim · Correct arithmetic still needs honest testing to mean anything.
  8. The field overfits the shared test; the number rises, real skill stalls · Collective tuning optimizes the test rather than the skill.
Worksheet · LightMySky