How Cached Indicator State Can Override CTA Initialization Data

Summary

A VeighNa community exchange addresses a CTA strategy whose indicators appeared unchanged after live initialization, while the strategy still placed orders. The user mentions a Dual Thrust strategy and uncertainty about whether a period running in no-UI mode updated indicator values. The reply explains that initialization first loads historical data to calculate indicators, then reads a prior cache file and overwrites the indicator state.

To investigate intraday updates, the respondent recommends printing indicator values from the bar callback. This can help distinguish a stale restored value from a value recalculated during live processing. The discussion does not establish whether the specific no-UI run updated indicators or explain how to inspect order records in that mode; the latter question receives only a brief reply. It is a narrow operational troubleshooting note, not a description or evaluation of the Dual Thrust trading method.

Key ideas

• Initialization may calculate indicators from historical data and then replace them with values restored from a cache.
• A restored cache can make displayed indicator values appear stale after startup.
• Logging indicator values from the bar callback can help track whether they update during live processing.
• The exchange does not resolve how to inspect order records in no-UI mode or verify the specific reported run.

Tags

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