Troubleshooting Live Data and Initialization in Simulated Trading
Summary
The post answers why a community-edition backtest can work while simulated trading produces no orders. It distinguishes imported historical data, which can be replayed during a backtest and used to initialize indicators, from simulated trading, where incoming real-time ticks or bars trigger strategy logic. It identifies missing market subscriptions, incorrect contract identifiers, failed strategy initialization, and insufficient history for an array manager as possible causes.
The suggested diagnostic steps include checking whether initialization completed, confirming that indicator variables hold meaningful values, reviewing logs for subscription failures, and verifying the contract and exchange. The response also describes using a data recorder to capture market updates and retain history for later initialization. These are software workflow recommendations, not a trading strategy or a measured performance study. The cited default requirement of 100 bars applies to the described array manager setup; required history and data availability may vary with configuration and interface.
Key ideas
- Backtest history and the live updates required to trigger simulated trading are separate data flows.
- A missing market subscription or mismatched contract can prevent strategy events from arriving.
- Insufficient history can leave an array manager uninitialized and block order logic.
- A data recorder can capture live updates and provide stored history for strategy initialization.
- Initialization status, variable values, and logs are useful diagnostic signals.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.