How VeighNa Load-Bar Initialization Depends on Historical Data
Summary
The post asks how VeighNa’s `load_bar(10)` initialization behaves in CTA strategies, especially when the user lacks an RQData subscription. It compares launching a backtest through VeighNa Studio with running one through a Jupyter-based backtesting engine, and asks whether missing initialization data prevents strategy startup or changes results. It also asks whether bars can be loaded from a local database.
The document presents these as unresolved questions rather than answering them. It gives a small initialization example and a backtesting setup, but no tests, results, or explanation of how `load_bar` obtains data. Readers should therefore treat it as a prompt for investigating historical-data configuration and warm-up requirements, not as evidence that a particular data source is necessary or that a failed load has a known effect on backtest validity.
Key ideas
- The post asks what historical data source supplies bars requested during strategy initialization.
- It compares CTA backtests launched in VeighNa Studio with runs from Jupyter.
- It asks whether initialization can proceed without an RQData subscription.
- It raises the possibility of loading warm-up bars from a local database.
- The post does not answer these questions or report experimental results.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.