Diagnosing Stale Moving Averages After Restarting a CTA Strategy
Summary
A VeighNa community exchange considers why a CTA strategy’s moving-average values may appear stale after pausing and restarting. The response suggests several possible causes: cached bar data not being restored or refreshed, strategy variables not being synchronized, and historical bars not being loaded again during initialization. It recommends checking the strategy’s initialization and startup process and inspecting logs or cached data to see whether fresh bars are available.
The discussion offers general troubleshooting ideas, including reloading history and reinitializing data-management components. It does not establish which cause applied to the questioner’s strategy, and it provides no follow-up showing that the proposed changes fixed the issue. Some suggestions, such as manually triggering an update or deleting a configuration file, are presented without supporting framework details. Treat the post as an initial checklist, not a confirmed diagnosis; actual behavior depends on the strategy’s lifecycle, data feed, and persistence setup.
Key ideas
- A paused strategy may resume with stale moving averages if its cached bars or internal state are not restored correctly.
- Reloading sufficient historical bars during initialization is one proposed way to refresh indicator inputs.
- The response recommends checking that strategy variables and data-management components are synchronized on restart.
- Logs and inspection of cached bar data can help determine whether fresh history was loaded.
- The forum exchange gives no verified cause or evidence that its proposed remedies resolved the reported problem.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.