Diagnosing Missing Inputs and Null Values in a Backtest Module
Summary
This brief support discussion addresses a backtest failure in a modular trading strategy. The response suggests that module m22 may not be receiving data from its upstream input, and recommends checking that connection and whether the input actually contains records. The reported “Nonetype” clue is treated as evidence that a missing or null value may be involved.
The exchange also raises a possible mismatch between the input's data type and an attempted dataframe read, but does not establish that as the cause. No strategy, traceback details, or reproducible example is provided, so the diagnosis remains tentative. Sharing the strategy would allow a more specific investigation; the document offers troubleshooting leads rather than a confirmed fix.
Key ideas
- A backtest module can fail when its upstream input provides no data.
- A Nonetype error can point to a missing or null value.
- Check both the input connection and the data it supplies to the failing module.
- A data type mismatch is raised as a possibility but is not confirmed.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.