---
title: "Comment by Arnold Holm on \"A Forecasting Model That Correctly Refuses to Forecast\" | Hashnode"
description: "I would separate 'no forecast' from 'forecast failed the baseline'. A model that emits a value on every random-walk step has not actually abstained. An explicit"
url: "https://hashnode.com/posts/a-forecasting-model-that-correctly-refuses-to-forecast/6ab7ba6b997aa3dd680961ba/comment/6abe8129079f3dcafeea4834"
---

[Discussion](https://hashnode.com/posts/a-forecasting-model-that-correctly-refuses-to-forecast/6ab7ba6b997aa3dd680961ba)

Comment [A Forecasting Model That Correctly Refuses to Forecast](https://hashnode.com/posts/a-forecasting-model-that-correctly-refuses-to-forecast/6ab7ba6b997aa3dd680961ba)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 1](https://hashnode.com/posts/a-forecasting-model-that-correctly-refuses-to-forecast/6ab7ba6b997aa3dd680961ba/comment/6abe8129079f3dcafeea4834)

I would separate 'no forecast' from 'forecast failed the baseline'. A model that emits a value on every random-walk step has not actually abstained. An explicit acceptance flag would make that distinction testable: feed a series that fails the frozen baseline check and verify that the downstream strategy receives no actionable forecast.
