Loss functions
Frame the regression loss workbench experiment
Page 1 advances one concrete regression loss workbench: explain the decision, run the code, inspect failure, measure evidence, and keep only what is ready to ship.
1Try it yourself
Playground
Loss landscape (lite)
Slide weight w. Loss = (w − 2)² is the training signal — gradient steps walk downhill.
Loss = (w − 2)² = 12.250
Before you start
Why this matters
Without running code, predict the output of this page's example and name the intermediate value that would prove your prediction. Then write one sentence answering: “What could look successful while actually being wrong?” For this stage, focus on wrong or deceptive loss signal. Keep the prediction nearby; comparing it with the real output is the first debugging exercise, not a quiz about syntax.
2Learn the idea
Read
Build focus
A lab needs a falsifiable claim before code. The claim here is that compare mean squared error and mean absolute error on ordinary predictions and one costly outlier. Record the tiny dataset, expected behavior, and one reason the result could be misleading. The first artifact is an experiment brief, not a model screenshot. It names the user, the decision the output supports, and the baseline you must beat. For this chapter, the baseline is deliberately transparent so later complexity has something honest to compare against.
The artifact's user-facing goal is specific: compare mean squared error and mean absolute error on ordinary predictions and one costly outlier. Its accepted input is equal-length finite numeric target and prediction lists. Those statements are intentionally narrower than “build an AI system.” Narrow scope lets us inspect every input and expected result, and it prevents a toy result from being presented as a production claim. Run the inventory below before implementing anything. Its output proves that the fixture is present and small enough to inspect by hand.
Read
Run the example
Save this as lesson.py and run python3 lesson.py. It uses only the language standard library, so the example is reproducible offline.
truth=[2,4,6,8]; pred=[2.5,3.5,6.5,12]
errors=[p-y for y,p in zip(truth,pred)]
print(errors)
Expected output: four signed residuals, with 4.0 largest. Exact floating-point formatting may vary slightly, but the asserted behavior must not. Read the output as evidence about this stage, not merely proof that the interpreter started.
Read
Debug the stage
Print every residual and transformed contribution before averaging. A single large squared term should visibly dominate MSE; if it does not, verify operand order, exponent placement, and the denominator. Reject unequal lengths because Python's zip silently drops extras. Reject NaN and infinity before aggregation, and keep target units visible so a mathematically correct score is not interpreted in the wrong scale.
At the experiment brief stage, save the smallest failing fixture beside the expected result. Change one cause at a time and rerun the exact command printed above; that makes the repair reviewable and keeps this chapter's progressive artifact reproducible.
Read
Evaluate before continuing
Compare MAE and MSE on the same holdout rows and show the largest contributor to each. Then translate the error into the product unit, such as minutes, dollars, or degrees. If underprediction costs more than overprediction, evaluate an asymmetric business cost separately; do not claim that minimizing a convenient textbook loss automatically minimizes operational harm.
For this experiment brief page, preserve the fixture and result as evidence for the next page. Label observations separately from conclusions: a passing assertion establishes the behavior it names, while broader usefulness requires the chapter's full evaluation set and stated operating limits.
Continue learning · glossary & guides
- [ ] What exact claim can this tiny fixture disprove?
- [ ] Which baseline prevents a decorative success claim?
- [ ] What result would make me stop before implementation?
- [ ] Can I explain which rows dominate each loss and why?