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 inputs we are comparing
Rows of matched procedure forecasts
Trend example
| 10 | 12 |
| 12 | 14 |
Model loses
| 10 | 10 |
| 14 | 16 |
Later observed outcomes
Trend example
- 012
- 114
Model loses
- 010
- 111
Result for trend example
- 02
- 10
A weekly rule faces an unusual middle day
This check uses the pieces from “Compare complete forecasting procedures on matched days”.
BOTIE
- Rows of matched procedure forecasts
15 15 15 10 20 10 - Later observed outcomes
- 012
- 124
- 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 →