FS1 8.1 - Type I and Type II errors
A statistical decision can be wrong in two different ways: rejecting a true claim or missing a real change. You will identify each error in context and calculate its probability using the correct population model and the test's fixed rejection rule.
Two ways a test can make an error
A test rejects a null hypothesis using a significance level. Does that mean there is a probability that this rejected hypothesis is actually true?
No. The significance calculation starts by assuming the null is true and asks how often the rule would reject it. That is a different direction of conditioning from asking whether the null is true after seeing a rejection.
You already know
A test has a null hypothesis , an alternative , and a critical region of outcomes that cause rejection. Earlier Poisson tests calculate probabilities under the null model; a conclusion of insufficient evidence does not prove .
To name an error, you need both the decision and the true population state. The observed count alone does not tell you whether a mistake has occurred.
Type I and Type II errors
A Type I error is rejecting when is true.
A Type II error is failing to reject when is false. Its probability is evaluated at a specified true alternative parameter.
For example, if says a machine's hourly fault mean is unchanged, a Type I error reports evidence of a change when there is none. A Type II error misses a change that really has occurred.
| True population state | Reject | Do not reject |
|---|---|---|
| is true | Type I error | Correct decision |
| The specified alternative is true | Correct detection | Type II error |
Neither error probability is the probability that a hypothesis is true. Also, Type I and Type II error probabilities are calculated under different population states, so they are not complements of each other.
Key idea
Keep truth and decision separate: Type I is a false rejection under the null, while Type II is a missed rejection under a specified true alternative.
The opening question reverses the condition. A significance limit controls false rejection when holds; it does not assign probabilities to the hypotheses after the data arrive.
False rejection is calculated under the null model
Once a rejection rule is fixed, its Type I error probability is the probability of that critical region under . Do not alter the cutoff during this calculation.
Probability of a Type I error
For a fixed critical region and a specified null parameter ,
The subscript records which true population parameter is used. For a discrete test this actual probability need not equal a stated significance limit. Not in the formula booklet: learn it.
Consider against , where is a population mean number of faults per hour. The statistic is a one-hour count, with a suitable Poisson model. Large counts lead to rejection.
Worked example 1: the false-alarm probability
Question. The fault test rejects when . Find the probability of a Type I error, to four decimal places.
Plan. Assume the null mean really is , and calculate the inclusive critical tail.
Why this step? A Type I error assumes the original mean is correct; replacing it with an increased mean would no longer measure a false alarm.
Answer. The Type I error probability is .
Check. This is below , consistent with the critical region constructed in the earlier Poisson lesson.
Worked example 2 changes only the rejection cutoff from to , making the rule more demanding.
Worked example 2: requiring a larger count
Question. Find the Type I error probability if the same hypotheses are tested by rejecting when .
Plan. Retain the true null distribution and move the tail boundary.
Why this step? The stricter rule rejects fewer outcomes, reducing the probability of a false rejection.
Answer. The probability is , to four decimal places.
Check. is contained in , so its probability must be smaller under the same model.
This reduction is not a free improvement in every respect. A rule that rarely rejects can also miss genuine changes; that is a separate calculation under the alternative.
Watch out
Wrong: multiply the critical-tail probability by an invented probability that is true. Right: Type I error is already a conditional calculation under a true null.
Raise the cutoff one more time.
A missed change is calculated under the alternative
Return to the original rule, rejecting for . If the mean has genuinely increased, a Type II error occurs when the observed count still lies in the non-rejection region .
The test's cutoff stays fixed. Change the probability model to the specified true alternative, rather than designing a new critical region using that alternative.
Probability of a Type II error
For fixed critical region , at a specified true alternative parameter ,
This is non-rejection under the true alternative model. Its value can change with ; it is not determined by the stated significance level alone. Not in the formula booklet: learn it.
The complement of concerns a correct detection under that same alternative. By contrast, a Type I probability uses the null parameter, so it cannot generally be found by subtracting from .
Worked example 3: missing a genuine increase
Question. For the rule , find the Type II error probability if the true hourly mean is , to four decimal places.
Plan. Use the actual mean , and sum the outcomes that fail to reject.
Why this step? The mean really has risen, so the error consists of observing too few faults for the fixed rule to detect the increase.
Answer. The Type II error probability is .
Check. A mean of is still below the rejection cutoff ; missing this change can be quite likely.
Continue this lesson.
You’re previewing NovaLearn without an account. Create a free account to read the rest.
Create free account