Skip to content
All library documents

Finding Backtest Logs and Print Output in VeighNa

Article vn.py community
Read the original

Summary

This forum exchange explains where to look when a VeighNa strategy backtest produces no visible trade records and a developer wants to inspect daily messages. The reply says scripted backtests expose log entries through the engine’s logs collection. For live CTA strategy operation, messages appear in the CTA interface; during backtest troubleshooting, print output can be viewed in the station’s Trading screen.

The advice is operational rather than a trading method, but it helps researchers diagnose strategy runs by identifying different output locations for scripted backtests, live trading, and station-based runs. It gives no code example, screenshots, or details about how to retrieve the log collection, and it does not explain why trade records might be missing. The guidance is specific to VeighNa’s interfaces and may not apply to other backtesting platforms.

Key ideas

  • Scripted VeighNa backtests expose log messages through the engine logs collection.
  • Live CTA strategy messages appear in the CTA interface.
  • Print output during station-based backtest troubleshooting can be viewed in the Trading screen.
  • The discussion does not explain causes of missing trade records or provide a full diagnostic procedure.

Tags

Backtesting

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