Analysis of test results and optimisation in the MetaTrader 5 strategy tester - page 15
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
Not everything is so simple.
Ilya Malev #:
"Аттракцион щедрости" в случае проскальзываний лимитов к ценам ближайших тиков
Stats.
on potic models like "OHLC" does not cancel it.
A generosity attraction for stop levels. I optimise through Virtual myself, so I can turn sliding on/off. However, sliding for stop levels is always on. Grails are not needed.
It's not that simple. Imagine a sequence of real ticks inside some bar
...
Show 4 control ticks that must be selected in this bar for all these orders on this bar to be triggered, as it will be in the "Real ticks" mode.
The principle of ascii generation is unfortunately not disclosed on the MQ side. I see that they do not coincide with the ones that were in reality, so there will obviously not be a full correspondence with real ticks, and the triggering of orders - too.
I think, with such (postictic) requests to the quality of testing, we should limit ourselves to OHLC M1 mode or generate a custom symbol with thinned real ticks according to our own principles (there are examples). It will be already very fast in any case, and chasing the mode at opening prices clearly implies a willingness to be more loyal to accuracy.
I think, with such (postictic) demands to the quality of testing, one should limit oneself to OHLC M1 mode or generate a custom symbol with thinned real ticks according to one's own principles (there are examples). It will be already very fast in any case, and chasing the mode at opening prices clearly implies a willingness to be more loyal to accuracy.
That's what I went down the path of creating a custom symbol in the beginning. I thought that turning OHLC into OHHLLC (O-Hbid-Hask-Lbid-Lask-C) would solve the problem. But it didn't solve the problem - it only introduced more discrepancies in the tests, so I didn't bother to look into the reasons further. Now I understand what the reason is - in the different mechanism of triggering orders in the Open Price Only mode and the Real Tick mode (for OHHLLC to work, you need to run the custom symbol in the Real Tick mode). Because in the first case the triggering will go without sliding, and in the second case with sliding, and if you make six ticks from one bar, especially if the bar is not M1, but for example H1, this sliding will make the test results obviously inadequate.
And take into account that the All ticks mode generates a stream of ticks from minute bars, i.e. within a minute the spread is fixed by the value that is set once in a minute bar (most likely by the value that was at the opening). Real ticks are the only adequate intra-minutes model in MT5 tester. I did not realise this for a long time and used All ticks everywhere in tests. Until one day recently I got a picture of a completely opposite profitability chart with the All ticks and Real ticks modes on one of my Expert Advisors (in that Expert Advisor there is a very close to the price trawl of orders, which was made within the spread).
sliding will make the test results obviously inadequate.
I assume that the trading mode of the account on which the tester is running or certain symbol specifications may enable the mode in the tester when there is no slip on real ticks.
Please specify which setting you are referring to
We need to get the documentation up. Netting, flippers, exchange, etc. For example, on the exchange, the limit must be executed exactly at the price. Most likely, this is taken into account in Tester.
Anyway, the account mode cannot be edited even in the custom symbol.
Find the demo account you need and run the Tester by connecting to it.