Why a BigQuant Run May Produce No Backtest Results

Summary

This platform troubleshooting note explains that a shared code sample may run without producing backtest data because it is incomplete. The reported sample lacks a data source and a backtest module, and contains only some backtest component methods. It also has variables that have not been defined. The discussion suggests checking whether the submitted code is the intended version before diagnosing the platform run further.

The note is about code completeness and the structure needed for a backtest, rather than a trading strategy or evidence about market behavior. It gives no detailed debugging procedure, corrected implementation, or example of how to connect a data source and backtest module. Its diagnosis is limited to the described sample, so it does not establish that these omissions explain every case of missing results in BigQuant.

Key ideas

• A code run may produce no backtest data when it lacks a data source.
• The described sample does not include the platform backtest module.
• Some variables in the supplied components are undefined.
• The note recommends checking whether the submitted code is complete and correct.
• It offers no general debugging guide or corrected code.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.