Complete Projects

Compare forecasts on the same later days

Accept the window where the fitted model loses

Botie needs tomorrow's water demand before tomorrow arrives. A project report must preserve the available history, stored forecasts, baseline, and matching later outcomes.

BOTIE

The baseline row [10, 10] and model row [14, 16] face actual demand [10, 11]. What should the report preserve?
The inputs we are comparing

Rows of matched procedure forecasts

Trend example

1012
1214

Model loses

1010
1416

Later observed outcomes

Trend example

  1. 012
  2. 114

Model loses

  1. 010
  2. 111
Result for trend example
  1. 02
  2. 10
Choose an explanation to test
A weekly rule faces an unusual middle day

This check uses the pieces from “Compare complete forecasting procedures on matched days”.

BOTIE

Botie compares two forecasting rules on the same three held-out days. The first row repeats a daily baseline; the second follows a fitted weekly pattern. Return each row's mean absolute error against the actual demand.
Rows of matched procedure forecasts
151515
102010
Later observed outcomes
  1. 012
  2. 124
  3. 212

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

Which changes to a future target should leave earlier stored forecasts unchanged, and how would you test that?

Retain origins, predictions, actuals, baseline errors, and fitted state. Audit calendar gaps and delayed readings before forming lagged inputs.

Forecasts must be stored before targets are observed. This workshop evaluates supplied predictions; fitting happens in the project code.

Work through the Python challenges →
Continue the courseCount Seeds While Keeping the Image Assumptions Visible →