Determines the verbosity of trade, error, and diagnostics messages (see Log). The more verbose, the slower the execution of large backtests.


0 Few messages. Most warnings are suppressed. Bars are only printed to the log in [Trade] mode or when trades are open.
1 More messages (default).
2 Even more messages. In [Trade] mode, the daily profit, drawdown, and CBI is printed once per day. In [Test] mode with TICKS flag any tick preceding a trade is printed in the log. The prices of the current asset at every bar are printed in the form Open/High\Low/Close.
3 Even more messages and warnings. Prices are displayed with more digits. Missing prices and internal function errors are displayed. In [Trade] mode, all open trades are listed once per day.
7 Extensive messages. Record memory allocations of 2 MB or more, broker API trade calls, and API execution times.
+ DIAG Additional flag to enable a 'black box recorder' for diagnostics. A ...diag.txt file is created in the Log folder. It contains a list with the last events and printf commands, and can be used to determine the reason of a crash or other problem that leads to the termination of the script. For details see troubleshooting. Black box recording strongly reduces the program speed, so do not use this flag unnecessarily.
+ ALERT Additional flag to display critical messages, such as suspicious asset parameters, possibly orphaned trades, broker API errors, or print(TO_ALERT,..) calls, in a separate alert box. DIAG recording is stopped at the first critical event, so the details leading to the situation can be evaluated from the black box log (Log\...diag.txt). Recording continues when the alert box is closed.
+ LOGMSG Additional flag to print the log also to the message window.





function run()
  Verbose = 7|DIAG; // extensive messages plus black box recorder 

See also:

LOGFILE, -diag, log, troubleshooting


► latest version online