Session 14
Charting & Trendlines
(Last session of the Foundations unit)
Why Plot?
A table of numbers can hide a lot — an outlier, a pattern, data that doesn't behave quite the way you expected.
A plot makes it visible at a glance.
Building the Plot
- Scatter plot: weight vs. displacement
- Add a linear trendline
- Display the equation
- Display R²
The Slope Tells You the Relationship
The slope of this line tells you the rate one thing changes relative to the other.
For a launcher, that's the whole idea behind calibration.
R² — What It Tells You
Closer to 1 = tighter fit.
R² — What It Tells You
It's diagnostic information, not a pass/fail grade — same idea as last session's conditional-formatting flags.
If R² Is Low — Don't Just Move On
Ask:
- Were a couple trials noisy? (measurement problem)
- Does the data genuinely behave non-linearly here? (real effect)
Different problems, different fixes.
You Could Also Compute This Directly
=SLOPE(y-range, x-range)
You Could Also Compute This Directly
=RSQ(y-range, x-range)
The chart isn't magic — it's the same functions skill from Session 12, just drawn as a picture.
Submit Today
Data table + plot + trendline + R² + a one-sentence diagnostic note on your fit quality.
Watch Out For
- Treating R² as a grade instead of information
- Assuming low R² always means "redo the experiment"
- Confusing the trendline's slope with individual data points
That's the Last New Skill in This Unit
Define, Design, Notebook, Safety, Measurement, Functions, Data Quality, Conversion, Tolerance, and now Charting — all of it was building toward one thing.
Next Up
The Launcher Project begins.
Same measure → log → chart workflow. Real stakes. Your own launcher.