VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Mathematics? | Bayesian Online Change-Point Detection for Condition Monitoring: Run Lengths, Hazard Functions, Predictive Evidence and False Alarms

Why mathematics is important becomes practical when a condition-monitoring stream changes suddenly and the question is not merely whether a reading is high, but whether the data-generating regime has changed. Bayesian online change-point detection, or BOCPD, maintains a probability distribution over run length: the number of observations since the latest change. A hazard function gives prior change probabilities, while predictive distributions score how compatible each new reading is with every possible current run.

For a compact teaching update, suppose the probability of no change before seeing the new reading is 0.90 and the change probability is 0.10. The reading has predictive likelihood 0.20 under continuation and 0.80 under a reset. The unnormalised masses are 0.90×0.20=0.18 and 0.10×0.80=0.08. Their total is 0.26, giving posterior probabilities about 0.6923 for continuation and 0.3077 for a change now. Stronger reset evidence raises the change probability, but the prior hazard still matters.

Full chapter index

Chapters 1–4 · Understand the question
  1. What counts as a change point
  2. Run length
  3. Run-length distribution
  4. Hazard function
Chapters 5–8 · Reproduce the example
  1. Predictive model within a run
  2. Growth probabilities
  3. Change probability
  4. Worked two-hypothesis update
Chapters 9–12 · Check assumptions
  1. Normalising evidence
  2. Conjugate updates
  3. Unknown mean and variance
  4. Pruning and truncation
Chapters 13–16 · Connect to condition monitoring
  1. False alarms
  2. Detection delay
  3. Outliers versus persistent changes
  4. Multiple sensors
Chapters 17–20 · Study and verify
  1. Covariates and interventions
  2. Retrospective verification
  3. Maintenance decisions
  4. Practice, misconceptions and next reading

CHAPTER 1 OF 20 · Understand the question

1. What counts as a change point

Back to contents

A change detector asks whether the recent data still belong to the same segment. A change point marks a shift in parameters governing the observations, not simply one unusual value. Mean vibration rises and remains at a new level. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. An outlier, trend and regime change are different hypotheses. Define the type and persistence of change.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use what counts as a change point as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Did You Know? BOCPD updates every plausible time since the last change at once; its central state is a distribution over run length, not a single alarm score. This is a useful reminder that an algorithm's name is shorter than the assumptions needed to use it well.

Contents · Next chapter

CHAPTER 2 OF 20 · Understand the question

2. Run length

Back to contents

Run length turns an unknown last-change time into a probability distribution that can be updated online. Run length records how many observations have occurred since the most recent change. Run length zero represents a change at the current step. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. It counts observations under the chosen convention, not necessarily elapsed hours. State indexing and timestamps.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use run length as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 20 · Understand the question

3. Run-length distribution

Back to contents

The alert is built from predictive evidence, not from surprise alone. The algorithm carries probability mass over many possible run lengths rather than one estimated last-change time. Both a recent switch and a long stable run remain plausible. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Summarising only the most probable run can hide uncertainty. Plot the full distribution or key credible sets.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use run-length distribution as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 20 · Understand the question

4. Hazard function

Back to contents

Sequential monitoring makes decision calibration as important as the recursion itself. The hazard gives the prior probability that a new segment begins after a run of a given length. A constant hazard implies a geometric prior on segment length. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. A convenient constant is not automatically physically justified. Use domain knowledge and sensitivity checks.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use hazard function as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Primary research: https://arxiv.org/abs/0710.3742. Check the authors' model, recursion and scope before transferring the method to a maintenance stream.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 20 · Reproduce the example

5. Predictive model within a run

Back to contents

A change detector asks whether the recent data still belong to the same segment. Each run-length hypothesis has a posterior predictive distribution based on data in its candidate segment. A stable Gaussian segment predicts the next vibration reading. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Independent-identically-distributed segments may be unrealistic for autocorrelated sensors. Choose an appropriate within-segment model.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use predictive model within a run as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Did You Know? BOCPD updates every plausible time since the last change at once; its central state is a distribution over run length, not a single alarm score. This is a useful reminder that an algorithm's name is shorter than the assumptions needed to use it well.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 20 · Reproduce the example

6. Growth probabilities

Back to contents

Run length turns an unknown last-change time into a probability distribution that can be updated online. If no change occurs, probability mass moves from run length r to r plus one and is weighted by predictive evidence. A reading consistent with the current segment grows long-run hypotheses. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Evidence depends on parameter uncertainty, not only distance from a point estimate. Use the full predictive density.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use growth probabilities as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 20 · Reproduce the example

7. Change probability

Back to contents

The alert is built from predictive evidence, not from surprise alone. If a change occurs, mass from all previous run lengths resets to zero through the hazard and reset predictive model. Several histories contribute to the same new-segment hypothesis. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Reset predictions require a defensible prior for new-segment parameters. Run prior predictive checks.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use change probability as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 20 · Reproduce the example

8. Worked two-hypothesis update

Back to contents

Sequential monitoring makes decision calibration as important as the recursion itself. Multiply continuation and change priors by their respective predictive likelihoods. Masses 0.18 and 0.08 normalise to 0.6923 and 0.3077. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. A likelihood ratio alone is not the posterior probability of change. Include prior odds.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use worked two-hypothesis update as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

HypothesisPrior probabilityPredictive likelihoodUnnormalised massPosterior probability
Continuation0.900.200.180.6923
Change now0.100.800.080.3077
Total0.261.0000
Two-hypothesis BOCPD teaching update.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 20 · Check assumptions

9. Normalising evidence

Back to contents

A change detector asks whether the recent data still belong to the same segment. The sum across all growth and reset paths is the predictive probability of the new observation. The teaching total is 0.26. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Tiny evidence can cause numerical underflow across long sequences. Use log-sum-exp or scaling.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use normalising evidence as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Did You Know? BOCPD updates every plausible time since the last change at once; its central state is a distribution over run length, not a single alarm score. This is a useful reminder that an algorithm's name is shorter than the assumptions needed to use it well.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 20 · Check assumptions

10. Conjugate updates

Back to contents

Run length turns an unknown last-change time into a probability distribution that can be updated online. Conjugate models can update sufficient statistics for each run length efficiently. Normal observations with unknown mean use running counts and sums. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Conjugacy is a computational convenience, not proof of fit. Check tails, autocorrelation and variance shifts.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use conjugate updates as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 20 · Check assumptions

11. Unknown mean and variance

Back to contents

The alert is built from predictive evidence, not from surprise alone. Student-t predictive distributions arise when mean and variance are integrated under common conjugate priors. Short runs produce wider predictions than long runs. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Prior hyperparameters strongly affect early detection. Report them and perform sensitivity analysis.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use unknown mean and variance as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 20 · Check assumptions

12. Pruning and truncation

Back to contents

Sequential monitoring makes decision calibration as important as the recursion itself. Implementation may discard very small run-length probabilities or cap the maximum run to control cost. A thousand-step stream keeps only material hypotheses. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Aggressive pruning can eliminate the true long-run history. Audit discarded mass.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use pruning and truncation as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Second authoritative source: https://www.cs.princeton.edu/~rpa/pubs/adams2007changepoint.pdf. Use it to compare notation, algorithmic conditions and the limits of the teaching example.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 20 · Connect to condition monitoring

13. False alarms

Back to contents

A change detector asks whether the recent data still belong to the same segment. Repeated online checking creates alerts even under stable operation unless thresholds and decision rules are calibrated. A 0.30 change probability may occur occasionally by chance. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Posterior probability is not the same as a guaranteed long-run false-alarm rate. Evaluate simulations and stable historical periods.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use false alarms as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Did You Know? BOCPD updates every plausible time since the last change at once; its central state is a distribution over run length, not a single alarm score. This is a useful reminder that an algorithm's name is shorter than the assumptions needed to use it well.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 20 · Connect to condition monitoring

14. Detection delay

Back to contents

Run length turns an unknown last-change time into a probability distribution that can be updated online. Higher thresholds or lower hazards can reduce false alerts while delaying detection. A safety-critical shift may justify faster review. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. There is no universally optimal threshold. Choose with consequence and workload data.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use detection delay as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 20 · Connect to condition monitoring

15. Outliers versus persistent changes

Back to contents

The alert is built from predictive evidence, not from surprise alone. A robust predictive model can absorb isolated extremes while sustained evidence builds a change hypothesis. One sensor spike is followed by normal readings. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Too-heavy tails can hide genuine abrupt shifts. Test both contamination and true-change scenarios.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use outliers versus persistent changes as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 20 · Connect to condition monitoring

16. Multiple sensors

Back to contents

Sequential monitoring makes decision calibration as important as the recursion itself. Joint predictive distributions combine evidence across channels and represent their dependence. Temperature and vibration shift together. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Multiplying marginal likelihoods assumes conditional independence. Model covariance or use structured features.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use multiple sensors as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 20 · Study and verify

17. Covariates and interventions

Back to contents

A change detector asks whether the recent data still belong to the same segment. Load, maintenance and operating mode can explain changes that should not be treated as unexplained faults. A scheduled speed increase changes vibration. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Ignoring known interventions creates avoidable alarms. Condition on recorded context.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use covariates and interventions as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Did You Know? BOCPD updates every plausible time since the last change at once; its central state is a distribution over run length, not a single alarm score. This is a useful reminder that an algorithm's name is shorter than the assumptions needed to use it well.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 20 · Study and verify

18. Retrospective verification

Back to contents

Run length turns an unknown last-change time into a probability distribution that can be updated online. Later data can confirm, revise or reject an online alert and refine the estimated change time. A persistent shift validates the earlier warning. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Retrospective certainty was unavailable at alert time. Preserve the original information set.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use retrospective verification as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 20 · Study and verify

19. Maintenance decisions

Back to contents

The alert is built from predictive evidence, not from surprise alone. A change probability becomes useful when combined with inspection costs, hazard consequences and alternative explanations. Route a moderate alert for review rather than automatic shutdown. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. Detection does not identify root cause by itself. Connect alerts to a documented response plan.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use maintenance decisions as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Useful next reading: condition monitoring, thresholds and false alarms, hidden-state sequence inference, Mathematics Learning Hub, eduKate Mathematics Learning System, approach to learning mathematics, Bukit Timah Mathematics curriculum overview, cross-subject learning approach. Each destination answers a different next question; choose by need rather than opening a link list at random.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 20 · Study and verify

20. Practice, misconceptions and next reading

Back to contents

Sequential monitoring makes decision calibration as important as the recursion itself. BOCPD joins Bayes' rule, conditional probability, recursion, predictive distributions and decision thresholds. Students can reproduce the 0.18 and 0.08 update before considering many run lengths. The quantity being updated must retain its definition, units and time boundary; otherwise a numerically tidy result can answer the wrong reliability question. A high change probability is model-conditional evidence, not proof that equipment is failing. Explain the prior, evidence, alternative models and action separately.

Here is the audit path. First, write the conditional statement in words. Second, list the inputs that were known at this step. Third, calculate or simulate the update without using later information. Fourth, inspect whether probabilities sum to one, covariance has the right units, and the result moves in a physically sensible direction. Save the hazard function, run-length support, within-run predictive model, priors, pruning rule and alert threshold. This record lets another reader distinguish evidence, approximation and judgement.

For a student, the transferable skill is to slow the calculation down. Use practice, misconceptions and next reading as the focus, then multiply continuation probability 0.90 by likelihood 0.20 and change probability 0.10 by reset likelihood 0.80, then normalise 0.18 and 0.08 to obtain 0.6923 and 0.3077. Predict which term should increase before touching a calculator. Change one defensible input and explain why the result changes. Finish by saying what the number supports and what it cannot establish. That final sentence prevents mathematics from being mistaken for certainty.

Quick answers

Why is mathematics important here? It makes the hidden assumptions, probability updates, uncertainty and decision consequences explicit enough to inspect.

Does the algorithm reveal the true physical condition? It estimates a model-defined state from data. Validation and engineering evidence are still required.

Which school mathematics transfers? Ratios, weighted averages, functions, graphs, probability, matrices and careful use of units all reappear.

What should a beginner calculate first? Reproduce the small numerical example, retain every intermediate value and explain the direction of the update.

What should a practitioner report? Data boundaries, model equations, priors or starting conditions, algorithm settings, diagnostics, sensitivity checks and the decision rule.

How should parents support learning? Ask the student to explain one symbol, one assumption and one limit. Clear explanation is evidence of understanding, not an extra task after the mathematics.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: What counts as a change point

Setup: Use this chapter’s illustrative case: Mean vibration rises and remains at a new level.

Task: Define the type and persistence of change.

Checking target: An outlier, trend and regime change are different hypotheses.

Practice case 2: Run length

Setup: Use this chapter’s illustrative case: Run length zero represents a change at the current step.

Task: State indexing and timestamps.

Checking target: It counts observations under the chosen convention, not necessarily elapsed hours.

Practice case 3: Run-length distribution

Setup: Use this chapter’s illustrative case: Both a recent switch and a long stable run remain plausible.

Task: Plot the full distribution or key credible sets.

Checking target: Summarising only the most probable run can hide uncertainty.

Practice case 4: Hazard function

Setup: Use this chapter’s illustrative case: A constant hazard implies a geometric prior on segment length.

Task: Use domain knowledge and sensitivity checks.

Checking target: A convenient constant is not automatically physically justified.

Practice case 5: Predictive model within a run

Setup: Use this chapter’s illustrative case: A stable Gaussian segment predicts the next vibration reading.

Task: Choose an appropriate within-segment model.

Checking target: Independent-identically-distributed segments may be unrealistic for autocorrelated sensors.

Practice case 6: Growth probabilities

Setup: Use this chapter’s illustrative case: A reading consistent with the current segment grows long-run hypotheses.

Task: Use the full predictive density.

Checking target: Evidence depends on parameter uncertainty, not only distance from a point estimate.

Practice case 7: Change probability

Setup: Use this chapter’s illustrative case: Several histories contribute to the same new-segment hypothesis.

Task: Run prior predictive checks.

Checking target: Reset predictions require a defensible prior for new-segment parameters.

Practice case 8: Worked two-hypothesis update

Setup: Use this chapter’s illustrative case: Masses 0.18 and 0.08 normalise to 0.6923 and 0.3077.

Task: Include prior odds.

Checking target: A likelihood ratio alone is not the posterior probability of change.

Practice case 9: Normalising evidence

Setup: Use this chapter’s illustrative case: The teaching total is 0.26.

Task: Use log-sum-exp or scaling.

Checking target: Tiny evidence can cause numerical underflow across long sequences.

Practice case 10: Conjugate updates

Setup: Use this chapter’s illustrative case: Normal observations with unknown mean use running counts and sums.

Task: Check tails, autocorrelation and variance shifts.

Checking target: Conjugacy is a computational convenience, not proof of fit.