Logging and Debugging Elite Backtests

Summary

This short forum exchange addresses how to inspect and debug backtests in the Elite trading environment. A beginner asks about getting output in the console or a log file, starting backtests from the command line, and using an editor with breakpoints. One reply recommends the platform’s write-log function for output and says the simulated version does not support launching scripts from the command line.

A follow-up asks where the logs are located; the response says that CTA strategy backtest logs run through the graphical interface are not written to a file. The exchange therefore offers a small amount of practical guidance about available logging and execution paths, but it does not explain where write-log output appears or describe a breakpoint workflow. It is a brief community Q&A rather than a complete debugging guide, and the information is specific to the Elite version and context discussed.

Key ideas

• The forum recommends using the platform’s write-log function to produce output during a backtest.
• The reply states that the Elite simulation version does not support starting scripts from the command line.
• The exchange says graphical-interface CTA backtest logs are not saved to a file.
• The discussion does not provide a detailed setup for breakpoints or explain the destination of write-log output.

Tags

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