The Settings Panel is used to specify all the settings needed to run tests or scans.
All these settings (except the active script name) can optionally be specified within a script.
This gives you the choice to either use this panel interface, a pure script-based approach, or a mixture of the two.
This panel can be hidden or shown using the View Menu or by pressing the F11 key.
The Settings Panel includes the following items:
Specifies a previously imported .RTD file to use in a test or scan.
This file is automatically loaded into memory (if not already there) when a script is run.
Use the load button to load it manually.
When any of the script run commands is chosen, it is applied to the currently active script window.
This will always be the script which was most recently opened or edited.
It is designated as "Active Script" in its title and its path is automatically shown in the "Active Script" field on the settings panel (if visible).
It is also possible to run any script without first opening it in a window by selecting it on the settings panel.
A script selected on the settings panel will remain active until a different script is selected or a script window is opened.
A place to type a brief note that will be displayed in the results window row for the test after it is run.
Specifies the amount of money to use in the simulated account when running tests.
Specifies the range of dates to use for the next test or scan.
Specifies the default data time period to use when running a script or using the debug panel. Currently supported bar sizes are Daily, Weekly, Monthly. Weekly and Monthly bars are derived from daily bars, so it is not necessary (nor supported) to import weekly or monthly data.
❖Use Available Bars
By default (unchecked), if any average or indicator can't be calculated because there are not enough bars since the start of the data, the return value is NaN (not a number). This automatically prevents all formulas from evaluating until they have enough bars to do so. If you wish to override this precaution and allow all averages and indicators to be calculated using however many bars are available, check this option. See Number of Bars Required for more details.
Specifies the level categories of trade records to keep in each test result record (each row of the Results window).
•Strategy - include normal strategy trades
•Benchmark - include benchmark strategy trades
•Skipped - include skipped trades (from each of the above categories if selected)
Specifies which type of additional output to create when a test is run besides the usual results data.
Available choices are:
•Report - generates the per-strategy and per-month summary report at the end of the test (reports can also be run manually for any test shown in the Results window)
•Graph - open a stats graph at the start of the test and updates it dynamically as the test runs (stats graphs can also be open manually for any test shown in the Results window)
•Log - generates a detailed transaction and position log and displays it at the end of the test (tests must be re-run to generate this log if not done previously)
•Orders - generate and display a list of hypothetical entry and exit orders to be placed for the day after the end of the test
•Scan - run a special scan allowing position-level formula elements to used to output the list of positions remaining open and/or other details
•Debug - break into the debug panel before closing end-of-test positions to allow full examination of the test context on the last date, and specify whether to show output from DebugEntry, DebugExit and DebugTargetStop statements in the script.