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? | Local Block Bootstrap: Slowly Changing Time-Series Structure

Why is mathematics important when a time series changes slowly, so blocks from distant dates are not exchangeable? The local block bootstrap resamples blocks from neighbourhoods near each target time. It preserves short-range dependence while allowing the data-generating structure to evolve across the record.

Did You Know? The method needs two scales: block length for dependence and locality width for gradual change. A good block can still be drawn from the wrong era if the neighbourhood is too wide.

Full chapter index

Chapters 1–7 · Understand the question
  1. The changing-structure question
  2. The research basis
  3. Target-time neighbourhoods
  4. A worked local window
  5. A worked block choice
  6. Two tuning parameters
  7. Slowly varying assumption
Chapters 8–14 · Reproduce the example
  1. Local centring
  2. Boundary handling
  3. Time scale
  4. Seasonality
  5. Evolving variance
  6. A local mean example
  7. A forecast example
Chapters 15–21 · Check assumptions
  1. A climate example
  2. Comparison with moving blocks
  3. Comparison with rolling windows
  4. Comparison with change-point methods
  5. Diagnostics
  6. Validation plan
  7. Limits
Chapters 22–28 · Explore applications
  1. A spreadsheet workflow
  2. A coding workflow
  3. Applications and careers
  4. A student investigation
  5. Common misconceptions
  6. Connection to recent mathematics articles
  7. Guidance for students and parents
Chapters 29–34 · Study and verify
  1. Practice questions
  2. Frequently asked questions
  3. A reporting checklist
  4. Two-scale geometry
  5. Final local-block audit
  6. Useful next reading

CHAPTER 1 OF 34 · Understand the question

1. The changing-structure question

Back to contents

Global block bootstrap assumes stationarity: a segment from the beginning can replace one near the end. Trends, evolving variance or gradual seasonal changes violate that exchangeability.

Contents · Next chapter

CHAPTER 2 OF 34 · Understand the question

2. The research basis

Back to contents

Paparoditis and Politis defined local block resampling for stochastic structure that changes slowly with time. Read the article abstract.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 34 · Understand the question

3. Target-time neighbourhoods

Back to contents

For a target position t, choose candidate block starts whose rescaled times lie within a locality bandwidth around t. Draw among those candidates rather than across the full record.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 34 · Understand the question

4. A worked local window

Back to contents

With n=100 and locality half-width 10, target t=60 uses candidate starts approximately 50 through 70, subject to block and boundary rules.

nTargetHalf-widthStarts
100601050–70
Local candidates.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 34 · Understand the question

5. A worked block choice

Back to contents

If block length l=5 and start 64 is selected, the copied block is positions 64–68. The next target location then chooses from its own local candidate set.

StartlPositions
64564–68
Selected block.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 34 · Understand the question

6. Two tuning parameters

Back to contents

Block length controls preserved dependence; locality bandwidth controls how quickly the resampling law may change. Their errors interact and should be tuned jointly.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 34 · Understand the question

7. Slowly varying assumption

Back to contents

Local stationarity means a short neighbourhood behaves approximately stationary while its parameters evolve over longer time. Sudden breaks need segmentation or break-aware methods.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 34 · Reproduce the example

8. Local centring

Back to contents

Means or trends may be estimated locally before resampling. Using a global centre can reintroduce the nonstationarity the method was designed to respect.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 34 · Reproduce the example

9. Boundary handling

Back to contents

Near time 1 or n, symmetric neighbourhoods are impossible. One-sided, reflected or adaptive windows change candidate probabilities and must be reported.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 34 · Reproduce the example

10. Time scale

Back to contents

Locality should be reported in observations and real time. A width of 20 means twenty minutes for one sensor and twenty months for another.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 34 · Reproduce the example

11. Seasonality

Back to contents

A local window must include appropriate seasonal phases or use seasonal alignment. Nearby calendar times can still be incomparable across weekday or season.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 34 · Reproduce the example

12. Evolving variance

Back to contents

Local resampling can preserve gradual variance changes if neighbourhoods are narrow enough. Too-wide windows mix low- and high-volatility eras.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 34 · Reproduce the example

13. A local mean example

Back to contents

Estimate uncertainty of a smooth time-varying mean by generating local block paths and recalculating the mean curve. Simultaneous bands need joint calibration.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 34 · Reproduce the example

14. A forecast example

Back to contents

The most recent neighbourhood may inform a near-future forecast better than old segments, but extrapolation beyond the observed evolution remains a modelling assumption.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 34 · Check assumptions

15. A climate example

Back to contents

Gradually changing seasonal amplitude may suit local blocks after careful detrending. Long-term forced trends should not be interpreted as resampling noise.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 34 · Check assumptions

16. Comparison with moving blocks

Back to contents

Moving blocks sample candidate segments globally under stationarity. Local blocks restrict candidates by target time to accommodate slow evolution.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 34 · Check assumptions

17. Comparison with rolling windows

Back to contents

A rolling analysis fits separate estimates to recent data. Local block bootstrap generates whole pseudo-series using time-varying candidate neighbourhoods.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 34 · Check assumptions

18. Comparison with change-point methods

Back to contents

Local methods assume gradual evolution. Change-point methods estimate abrupt regimes; mixing the two without a model can blur genuine breaks.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 34 · Check assumptions

19. Diagnostics

Back to contents

Plot candidate windows, local means, variances and autocorrelations. Check how often each original time is selected and whether generated paths preserve evolution.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 34 · Check assumptions

20. Validation plan

Back to contents

Simulate locally stationary processes and abrupt-break alternatives, vary both bandwidths, measure coverage and compare with global blocks and segmented bootstraps.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 34 · Check assumptions

21. Limits

Back to contents

Local blocks can fail when change is abrupt, neighbourhoods are sparse, seasonality is misaligned, dependence exceeds l or future evolution is extrapolated without support.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 34 · Explore applications

22. A spreadsheet workflow

Back to contents

Create rows for target time, local candidate range, selected start, copied block and boundary adjustment. Plot candidate coverage across the record.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 34 · Explore applications

23. A coding workflow

Back to contents

Unit-test n=100, t=60, width 10 gives candidates 50–70 and l=5 at start 64 gives 64–68. Save both tuning parameters and seed.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 34 · Explore applications

24. Applications and careers

Back to contents

Local resampling matters in climate, finance, health monitoring and sensors. Careers require nonstationary time-series reasoning, computation and scientific context.

Contents · Previous chapter · Next chapter

CHAPTER 25 OF 34 · Explore applications

25. A student investigation

Back to contents

Simulate a gradually rising AR variance and an abrupt break. Compare global and local block coverage across locality and block grids.

Contents · Previous chapter · Next chapter

CHAPTER 26 OF 34 · Explore applications

26. Common misconceptions

Back to contents

Local does not mean independent, nearby times are not always seasonally comparable, and gradual-change methods do not automatically detect breaks.

Contents · Previous chapter · Next chapter

CHAPTER 27 OF 34 · Explore applications

27. Connection to recent mathematics articles

Back to contents

The moving-block guide explains global blocks. The block-length guide explains dependence tuning.

Contents · Previous chapter · Next chapter

CHAPTER 28 OF 34 · Explore applications

28. Guidance for students and parents

Back to contents

Students should draw candidate windows on a timeline. Parents can ask which changes are treated as gradual structure and which are treated as random variation.

Contents · Previous chapter · Next chapter

CHAPTER 29 OF 34 · Study and verify

29. Practice questions

Back to contents

  • Find candidates 50–70.
  • List block 64–68.
  • Separate both bandwidths.
  • Diagnose an abrupt break.
  • Handle boundaries.

Contents · Previous chapter · Next chapter

CHAPTER 30 OF 34 · Study and verify

30. Frequently asked questions

Back to contents

### Is the full record exchangeable? No.

### How many tuning scales? At least block and locality widths.

### Does it model abrupt breaks? Not by itself.

### Why use real time units? Sampling intervals differ.

Contents · Previous chapter · Next chapter

CHAPTER 31 OF 34 · Study and verify

31. A reporting checklist

Back to contents

Report time scale, local-stationarity assumption, block length, locality width, candidate rule, edges, seasonality, B, seed, diagnostics and break sensitivity.

Contents · Previous chapter · Next chapter

CHAPTER 32 OF 34 · Study and verify

32. Two-scale geometry

Back to contents

The dependence block determines what moves together; the locality window determines where that block may come from. Confusing these roles produces plausible-looking but invalid paths.

Contents · Previous chapter · Next chapter

CHAPTER 33 OF 34 · Study and verify

33. Final local-block audit

Back to contents

Confirm slow evolution, separate tuning scales, valid seasonal matching, transparent edges, candidate-coverage diagnostics and explicit failure under abrupt change.

Contents · Previous chapter · Next chapter

CHAPTER 34 OF 34 · Study and verify

34. Useful next reading

Back to contents

Continue through the Mathematics Learning Hub. Rebuild one block, taper, local-neighbour or regeneration calculation by hand before trusting automated output.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Plot evolving series

Setup: Start from the article’s local-block mechanism for case 1. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 2: Choose block length

Setup: Start from the article’s local-block mechanism for case 2. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 3: Choose locality width

Setup: Start from the article’s local-block mechanism for case 3. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 4: Select target time

Setup: Start from the article’s local-block mechanism for case 4. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 5: Find candidate starts

Setup: Start from the article’s local-block mechanism for case 5. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 6: Draw start

Setup: Start from the article’s local-block mechanism for case 6. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 7: Copy block

Setup: Start from the article’s local-block mechanism for case 7. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 8: Advance target

Setup: Start from the article’s local-block mechanism for case 8. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 9: Handle left edge

Setup: Start from the article’s local-block mechanism for case 9. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 10: Handle right edge

Setup: Start from the article’s local-block mechanism for case 10. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 11: Use local centring

Setup: Start from the article’s local-block mechanism for case 11. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 12: Align season

Setup: Start from the article’s local-block mechanism for case 12. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 13: Model trend

Setup: Start from the article’s local-block mechanism for case 13. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 14: Model variance

Setup: Start from the article’s local-block mechanism for case 14. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 15: Increase locality

Setup: Start from the article’s local-block mechanism for case 15. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 16: Reduce locality

Setup: Start from the article’s local-block mechanism for case 16. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 17: Increase block

Setup: Start from the article’s local-block mechanism for case 17. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 18: Add gradual change

Setup: Start from the article’s local-block mechanism for case 18. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 19: Add abrupt break

Setup: Start from the article’s local-block mechanism for case 19. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 20: Compare global blocks

Setup: Start from the article’s local-block mechanism for case 20. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 21: Change seed

Setup: Start from the article’s local-block mechanism for case 21. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 22: Increase B

Setup: Start from the article’s local-block mechanism for case 22. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 23: Audit candidates

Setup: Start from the article’s local-block mechanism for case 23. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 24: Name limits

Setup: Start from the article’s local-block mechanism for case 24. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 25: Write conclusion

Setup: Start from the article’s local-block mechanism for case 25. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the dependence unit, verify the weight, window or cycle identity, and state one diagnostic before interpretation. Record the units and compare with one defensible alternative. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.