MTP Settings Explained

Introduction

This guide provides an overview of the key settings for the MTP and how to configure them for optimal backtesting. If you haven’t installed the MTP yet, please reach out to your support team for installation assistance.

1. Terminal Settings Overview

The terminal settings are divided into several subcategories: terminal settings, time frame, base directory, and tester settings.

Master Terminal

The Master Terminal refers to the MT5 account you're using for backtesting. Common brokers include Alpari, E8, Fxify, or ICMarkets. You need to ensure that the terminal you select matches the broker account of the strategy you are testing. For example:

• If the strategy is designed for Alpari, ensure that Alpari is set as the Master Terminal.

Master EA (Expert Advisor)

The Master EA is the version of the Titan expert advisor used in the strategy. To find the correct version:

• Check the leaderboard to see which version of Titan the strategy is built for.
• Select the matching version in your MTP setup (e.g., Titan 23.04).

2. Parallel Terminals Configuration

The Parallel Terminals setting defines how many CPU cores or threads are utilized during the backtest.

Core Allocation

To avoid overloading your VPS (Virtual Private Server):

• Do not use all available cores for backtesting. This could max out your VPS capacity, causing overheating or system resets.
• For example, if your VPS has 8 cores, only allocate 4 cores to the backtest.
• If you have a 4-core VPS, allocate 2 cores for the backtest to leave room for other processes.

Running Terminals Minimized

Make sure to check Run Terminals Minimized. Leaving this unchecked will flood your screen with numerous terminal windows, making it difficult to manage.

3. Time Frame Settings

The Time Frame defines the duration over which the backtest will run.

Recommended Time Frame:

• Always choose a one-year period for comprehensive data and reliable results.
• Testing over shorter periods (like a week or a month) provides less meaningful data.
• For more thorough backtesting, aim for a period longer than one year, if possible.

Time Frame Configuration:

• Start Date: It's recommended to start from June 2023 to the current date.
• Increments: Set the increments to 1.
• Chunk Size: Set this to 99 for optimal performance.
• Skip Weekends: This option should be enabled to avoid unnecessary data from non-trading days.

4. Base Directory and Tester Settings

You don't need to manually adjust the Base Directory; it's handled automatically.

Tester Settings

In the Tester Settings, you'll select the strategy you want to backtest. Follow these steps:

• Choose the desired strategy file (e.g., Pick Best).
• Depending on the strategy, certain values, such as time frame or version, will update automatically to fit the selected strategy.

5. Running a Backtest

Once all the necessary settings are in place, you can run the backtest.

Steps to Run a Backtest:

1. Select a Shorter Time Frame if you're doing a quick demonstration (e.g., a few weeks instead of a year).
2. Choose the Correct Broker and Titan Version based on your strategy.
3. Start the Backtest: Click the Start button to initiate the backtest.

Note: If there are any issues during the backtest due to conflicting installations, such as a previously installed copy of a strategy, it might interfere with the test. Make sure no conflicting copies are active on the terminal to ensure smooth operation.

6. Reviewing Backtest Results

Once the backtest is completed, you can view the results either through the Report Parser or the Results Folder.

• Report Parser: This tool simplifies viewing data, showing the pass rate, number of failed challenges, average days, equity peaks, and more.
• The detailed report will give you insights similar to those available on the leaderboard.

By following these steps, you will be able to effectively configure and run backtests on the MTP.