---
title: "Comment by Kartik N V J K on \"Building a Decision-Support Framework When No Dataset Exists\" | Hashnode"
description: "The leave-one-season-out call is the right instinct. With five seasons the failure mode is exactly what you named: sharp on training data, dead on a season it n"
url: "https://hashnode.com/posts/building-a-decision-support-framework-when-no-dataset-exists/6a8e4eb8edd516b00712ad91/comment/6a8f3494194331e55bc51743"
---

[Discussion](https://hashnode.com/posts/building-a-decision-support-framework-when-no-dataset-exists/6a8e4eb8edd516b00712ad91)

Comment [Building a Decision-Support Framework When No Dataset Exists](https://hashnode.com/posts/building-a-decision-support-framework-when-no-dataset-exists/6a8e4eb8edd516b00712ad91)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 26](https://hashnode.com/posts/building-a-decision-support-framework-when-no-dataset-exists/6a8e4eb8edd516b00712ad91/comment/6a8f3494194331e55bc51743)

The leave-one-season-out call is the right instinct. With five seasons the failure mode is exactly what you named: sharp on training data, dead on a season it never saw. I would also slice-check the rare states, since an 8-state space can hide a class showing up only a few times. Did any state end up too sparse to trust?
