Offline Vs Field
TODO:
- [ ] Add page-specific notes for
model-evaluation/comparisons/offline-vs-field.mdafter inspecting the real project files. - [ ] Cross-link
Offline Vs Fieldto the most relevant code, data, testing, and safety pages. - [ ] Define the metric or field result in one precise sentence.
- [ ] List the script, command, or notebook that produces this result.
- [ ] List the exact dataset split, label file, and model versions being compared.
- [ ] Mark whether results are current or historical.
- [ ] Add units, thresholds, and interpretation rules.
- [ ] Add how this result can disagree with real field behavior.
- [ ] Add the retest checklist needed after labels or runtime code changes.
- [ ] List model file path, version, preprocessing path, output scale, and known field behavior.
- [ ] Add current vs historical metrics once retesting is complete.
- [ ] Add test date, time, weather, route, model version, and manual takeover count.
- [ ] Add what failed, what worked, and what data should be collected next.
- [ ] Add the exact source path, artifact path, or hardware component name.
- [ ] Add the command or procedure needed to reproduce the result.