Analysis of test results and optimisation in the MetaTrader 5 strategy tester - page 14

You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
The task was to make the tester take into account, when checking the execution of orders on a given bar, high and low-ask in the testing mode Only bar opening (for example, H1).
You can play with MqlRates.spread to achieve High/Low-ask. I don't know how this field affects the generation of asks now.
The task is really to find the golden mean between accuracy and speed. It might make sense to thin the ticks a lot and use the corresponding custom symbol in the real ticks mode.
The challenge is actually to find the golden mean between accuracy and speed. Perhaps it makes sense to thin the ticks a lot and use the corresponding custom symbol in the real ticks mode.
You can try it that way.
You could try it that way.
The problem is that if we use wildcard ticks instead of just the opening prices, making the Real ticks mode, the orders will be executed not at the price of their placing (as in the Just opening prices mode), but at the prices of the first ticks after their crossing, which will be absolutely inadequate execution if there are only a few ticks per hour. On this basis:
Yes.
The problem is that if we use wildcard ticks instead of just the opening prices, making the Real ticks mode, the orders will be executed not at the price of their placing (as in the Just opening prices mode), but at the prices of the first ticks after their crossing, which will be absolutely inadequate execution if there are only a few ticks per hour. Proceeding from this:
Executing with slippage is the norm.
they rarely slip in practice at all.