Statistics 1
Deep Dive: Correlation Coefficient and Regression Calculation
CODEX Deep-Dive — The Product Moment Correlation Coefficient: Calculation, Mechanism, and Real Exam Angles (WST01 spec 4.3)
Provenance, 2026-09-29 (revised same day on re-read): written after reading
research/veridian/WST01-verified-facts.md in full (§1–§2b, §4 "Section 4", §7–§8, the per-lesson
audit entry for wst01-correlation-coefficient-and-regression-calculation, and — on this revision —
also the per-lesson audit entry for wst01-regression-gradient-interpretation-extrapolation.ts, which
this document's first draft had grepped for PMCC content but not read in full), the existing lesson
file content/veridian/curriculum/wst01/correlation-coefficient-and-regression-calculation.ts in full
(including its own header note and closing flag block, which carry a documented correction to the
facts bank — see §5 below), the four other existing technique-hub documents in this folder
(codex-formula-and-method-bank.md §1.3/§2.4, forge-exam-technique-guide.md §3.2 and its trap
table, signal-frequency-and-boundaries.md §1, and —on this revision —
signal-topic-brief-correlation-coefficient-and-regression-calculation.md, which independently caught
and corrected the same undercount §4 fixes below), and content/veridian/question-bank/wst01.ts
(grepped for "correlation"/"PMCC"/"regression" — zero matches; this sub-topic has no question-bank
entries at all). All new arithmetic below was computed independently with Python and is flagged as
such at each point it appears; nothing below is asserted as a Pearson-published answer unless a
specific document and question number is named for it.
Why this document exists, and what it does not re-teach
The lesson file this topic is drawn from says plainly, in its own header, that spec item 4.3 — the product moment correlation coefficient — has "the thinnest evidence base of any WST01 lesson in this batch": exactly two primary-source anchors (one examiner report, one mark scheme), against five for its sibling topic (regression-gradient interpretation and extrapolation, spec 4.1/4.2). That lesson already teaches, in full, and this document does not repeat: the recap, the formula itself, the unit-cancellation argument for why is bounded, a full algebraic derivation of coding invariance including the sign-flip edge case, a chain-drill on coding, four MCQs, and a seven-mark worked example (tutor revision hours vs. test score, , , , ) with its own common-wrong-path. Reproducing any of that here would be restatement, not depth.
What follows instead is three things the reviewed archive supports but no existing WST01 document currently states: (1) a proof, rather than an assertion, of why always holds; (2) an explicit derivation connecting the two printed forms of // (deviation and computational), which every WST01 document that uses them states without deriving; (3) a quantitative reconstruction — using real, already-published summary statistics from a genuine WST01 question — of exactly how large the documented substitution error actually is, and what wrong final answer it would produce, neither of which the facts bank or any lesson currently computes. It closes with a synthesis of every real exam angle the reviewed archive has actually tested spec 4.3 from, with the honest denominator attached to each one.
1. What the spec and formula booklet actually require
Spec item 4.3, verbatim (spec pp. 53–56, transcribed in the facts bank §1): "The product moment correlation coefficient, its use, interpretation and limitations. (Guidance: derivations and tests of significance will not be required.)" Three things are named as content in their own right — use, interpretation, limitations — not just the calculation, and "derivations... will not be required" is an explicit statement that a student never has to reproduce §3 of this document in an exam. It is included here as background understanding, in the same spirit as the lesson's own beyond-spec block on coding invariance.
The formula booklet (facts bank §2a, Issue 2, January 2021, pp. 13–17) prints, in full, both forms of , , , the PMCC formula , and the regression coefficient . Nothing in this document's §2–§3 needs memorising for that reason — every formula used below is either printed in the booklet or derived from what is.
2. The calculation model, in full
2.1 Why the "deviation" and "computational" forms of are the same formula
Every WST01 document that uses states both forms side by side (booklet, both lessons, the CODEX formula bank) but none derives why they're equal — worth doing once, because the substitution trap covered in §4 below is exactly a failure to respect this equivalence. Expand the deviation form:
Since , the middle term is , so the last two terms combine to . That gives , and since , this is exactly — identical to the printed computational form. follows by relabelling throughout. follows the same expansion with two variables: , and substituting , collapses the last three terms to , giving — again exactly the printed form. This is the reason the mean-squared substitution error (§4) is a different number, not a rounding variant of the correct one: (correct, appears once, already divided by inside and then multiplied back by ) and alone (wrong, missing that factor of ) are related by a factor of itself — for , as in the real question below, a twelve-fold-scale error hiding inside a subtraction.
2.2 The PMCC formula and what it measures
answers "how much does change per unit of "; answers "how tightly do the points cluster around a straight line, in both directions at once" — a comparison of the association () against the product of both variables' own spreads, rather than 's comparison against 's spread alone. Both lessons already establish, correctly, that this is why is unit-free and is not; §2.3 below proves the boundedness that follows from it, rather than asserting it.
2.3 Why always holds — a real proof, not an assertion
Spec 4.3 explicitly waives derivations, and the existing lesson's mechanism block argues boundedness by unit-cancellation — a real and sufficient argument for why has no units, but not, on its own, a proof of the specific bound . Here is that proof, standard for any dataset and worth having once in this course since nowhere else states it:
For any real number , and writing , :
— true for every , since it is a sum of squares. Expanding:
This is a quadratic in (coefficients , , ) that is never negative for any real — which is only possible if its discriminant is :
Dividing both sides by (positive for any real dataset with more than one distinct - and -value) gives directly — is not a convention or a coincidence of the formula's construction, it is a forced consequence of every real number squared being non-negative. Equality () holds exactly when the discriminant is zero, i.e. exactly one makes the sum-of-squares zero, which happens only when every single point satisfies — the data lies exactly on a straight line through . This is genuinely additional depth beyond what spec 4.3 requires (its own guidance waives derivations), included because it converts " is always between and " from a memorised fact into a checkable one.
3. Micro worked examples, one per real distinct sub-case
Each dataset below is small, original to this document, and independently verified by Python before being written in; none reuses a dataset from either existing lesson.
3.1 — Computing from raw data. : 1, 2, 3, 4, 5; : 3, 5, 4, 8, 10. , , . Computing the three sums directly: , , . Then (3 s.f.) — a genuinely strong positive linear association, consistent with rising fairly steadily as does.
3.2 — The same data, linearly coded, confirming invariance numerically. Coding and (arbitrary positive constants, chosen only to be different from either existing lesson's coding examples) on the identical five points gives , , , and — identical to 3.1's to full precision, matching the mark-scheme-credited property " not affected by (linear) coding" (Jan 2024 MS, Q2(d)) on a dataset built specifically to check it, rather than merely citing it.
3.3 — Quantifying the real substitution trap on its own real numbers. The facts bank's
audit trail (its own per-lesson audit entry for wst01-regression-gradient-interpretation-extrapolation.ts)
discloses the actual data line for the genuine question this trap comes from — Pearson Edexcel WST01/01,
October 2021, Q2: , , (given), ,
, — and the confirmed real error, quoted directly from the
examiner report: "the most common error made was using in the calculation of ."
Neither the facts bank nor either existing lesson computes what that substitution actually does to the
answer. Doing so here, from these disclosed figures: the correct
;
the wrong path substitutes for the correction term
directly, giving — over fifteen times larger
than the correct value (ratio ), not a rounding-scale difference. Carrying this into the
PMCC step it feeds (using the also-disclosed ): the correctly-computed
, while the wrong- path gives
— a wrong answer that still lands
comfortably inside and so trips no " means a mistake" self-check, the identical
danger the existing lesson already documents for the separate sqrt-omission trap on a different real
question (Jun 2024 Q4(b)). Caveat, stated plainly: these -values are this document's own
computation from the summary statistics the facts bank discloses for this question, not an
independently verified transcription of a printed mark-scheme target for Oct 2021 Q2(b) — that exact
printed figure was not confirmed in the source material this document read.
3.4 — Why "linear-only" is a real mathematical limitation, not a hedge. : ;
: — a perfect, entirely deterministic relationship (every -value is exactly
predictable from ). Computing directly: , , , ,
and exactly, so
exactly — the strongest possible relationship producing the weakest possible
PMCC reading, because the relationship is symmetric about the line and curved rather than
straight. This is the concrete arithmetic behind the teach block's own claim (that near 0 can
coexist with a genuine, strong, non-linear relationship) and behind MCQ pmcc-mcq-4's U-shaped
scenario in the existing lesson — this document supplies the worked numbers that claim was previously
stated in words only.
4. Synthesis: every real exam angle spec 4.3 has actually been tested from
Stated with the facts bank's own honest denominators throughout (§3 of the facts bank: 6 series with a fully-read examiner report, 14 series with a verified mark scheme).
| Real angle | Confirmed in | Source type | What it actually tests |
|---|---|---|---|
| Calculating from summary sums, direct formula substitution | Jun 2024 Q4(b) | Examiner report + mark scheme (1 of 6 ER series) | The formula itself; "answered well" per the ER, but with one specific common error (next row) |
| Omitting the square root in the denominator | Jun 2024 Q4(b) | Examiner report, verbatim (1 of 6) | Dividing by directly instead of — produces a small, in-range, wrong number, not an out-of-range red flag |
| Mean-squared substituted for the computational correction term inside an -formula feeding a PMCC calculation | Oct 2021 Q2(b) (, not — see §3.3) | Examiner report, verbatim (1 of 6) | The identical algebraic slip §2.1 derives against, quantified in §3.3 above |
| PMCC invariant under linear coding | Jan 2024 MS Q2(d) | Mark scheme only (1 of 14; no ER located for this series) | A credited general-knowledge property, not a calculation step in itself |
| Calculating and interpreting (as parts (a)–(b) of a wider regression question) | Jun 2022 Q2(a)–(b) | Confirmed present by direct re-reading of the real question paper (sibling lesson's own audit trail); no specific quoted wrong-answer mechanism survives in the facts bank's own written summary for these two parts | Confirmed-present-but-undetailed: this document's first draft, working only from the facts bank's own §4 "Section 4" prose and this sub-topic's own audit entry, missed this citation entirely — caught on this revision by reading the sibling lesson's audit entry directly, and independently, by signal-topic-brief-correlation-coefficient-and-regression-calculation.md in this same folder |
| "Give values to the required accuracy" discipline on this same paper | Jun 2024 Q4(c) | Examiner report, verbatim (1 of 6) | Correctly attributed to the regression line's gradient step, not to — the lesson file's own header documents a correction made after independently re-fetching the real mark scheme (WST01_01_2406_MS) and examiner report (WST01_01_2406_ER); this document defers to that corrected account, since the facts bank's own §4 write-up of this quote (as of this reading) still describes it as a "show that... then r" question, which the primary documents contradict |
| Use, interpretation, and limitations of (linear-only measurement, no causal claim, no guarantee beyond the data's own range) | Not found as a standalone tested example in the reviewed archive | Facts bank §4 states this directly; the existing lesson's own teach block says the same | Required by spec 4.3's own wording as content, independent of whether a past-paper example tests it directly |
| Section-wide frequency (spec 4.1–4.3 combined, not 4.3 in isolation) | 4 of 6 ER series (Oct 2021, Jun 2022, Jan 2023, Jun 2024), plus mark-scheme-only confirmation in Jan 2024 | Signal-frequency document | 14 of 75 marks in the one series with a full breakdown (Jan 2023, Q6) — this figure covers the whole correlation-and-regression section, not the PMCC sub-skill alone; no citation found confirming which, if any, part of Jan 2023 Q6 specifically tests 4.3 |
What this table does not contain, on purpose: a percentage or fraction of series in which spec 4.3
specifically (as opposed to the wider 4.1–4.3 section) appears, even though the count is now pinned
down more precisely than this document's first draft managed. Spec 4.3 itself — a PMCC calculation,
interpretation, or named property, as distinct from the section's regression-line content — is
confirmed present in 3 of the 6 fully-read ER series (Oct 2021, Jun 2022, Jun 2024) plus 1
mark-scheme-only citation (Jan 2024). The Jun 2022 instance is confirmed only by direct re-reading of
the real question paper (recorded in the sibling lesson's own audit trail, and independently by
signal-topic-brief-correlation-coefficient-and-regression-calculation.md in this folder) — no
specific quoted wrong-answer mechanism for Jun 2022 Q2(a)–(b) survives in the facts bank's own written
§4 prose, which is why this document's first draft, reading only that prose, undercounted it as 2 of
6. Stating a rate finer than "3 of 6, on this denominator, dated and named" — e.g. converting it to a
year-over-year trend or a percentage of all 14 series — would still be exactly the kind of
manufactured-precision this course's standing rules forbid, since only 6 of the 14 series have a
fully-read examiner report at all.
5. What remains flagged, not resolved, by this document
- The facts bank's own §4 "PMCC use and limitations (4.3)" paragraph, read as delivered, still describes the Jun 2024 Q4(c) accuracy quote as belonging to a "show that... then r" question. The correlation-coefficient lesson file's header documents, with specific re-verified numbers (, , , gradient , intercept ), that this is a mischaracterisation and that the quote belongs to the regression line's gradient step, not to . This document follows the corrected account throughout §4 above; the facts bank text itself has not been re-edited to match, as of this reading.
- This document's own first draft undercounted spec 4.3's frequency as "2 of 6" fully-read ER series, having read this sub-topic's own audit entry in the facts bank but not the sibling lesson's — which records that its Jun 2022 Q2(a)–(b) tests spec 4.3 directly. Fixed on this same-day revision (§4 above now reads "3 of 6"); noted here as a correction actually made, not merely a risk flagged, since the wrong count had already been written once.
- §3.3's reconstructed -values for Oct 2021 Q2(b) are this document's own arithmetic from disclosed summary statistics, not a confirmed transcription of a printed answer — stated plainly there and repeated here so it isn't missed.
- No standalone past-paper example testing 's interpretation or limitations directly was located in the reviewed archive; §2.2's discussion and the existing lesson's teach block both rest on the spec's own wording, not on a quoted exam instance, and both say so.
- This document performed no new PDF fetches or searches; every cited fact traces to
research/veridian/WST01-verified-facts.md, the existing lesson file's own header/flag block, or this document's own independently-verified arithmetic on numbers those two sources already disclose.