Development plans for the MetaTrader 5 Strategy Tester - page 17
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
I don't understand the script. Why would the developer put an EA in the Market that suspends it in the Visualizer in a certain situation?
This is sometimes necessary when your robot allows you to trade manually. For example, I have an EA mode. The robot tells what to do and the user has to press the appropriate button right on the chart.
And then you should automatically reduce the speed of the tester. In this mode the robot can work as a trainer. I use about 10 to 15 "Comment" commands for this, which at the right moment significantly reduce the speed of testing :)
Got it, thank you.
Use while when you want to stop the tester.
In the loop, check the condition of resumption of work.
It is very useful for any robot to stop at the opening and closing of positions to see the signal.
Use while when you want to stop the tester.
In the loop, check the condition of resumption of work.
It is very useful for any robot to stop at the opening and closing of positions to see the signal.
This trick doesn't work in MT5 unfortunately - when you exit the loop the history is scrolled instantly for as many days ahead as the tester would have passed during that time without looping. Sounds strange, and looks even stranger on a chart, I hope you get my point))
Debug mode is extremely inconvenient for testing strategies (not code). In MT4 you could implement in the visual tester scrolling +1 bar, +1 tick, etc., as much as imagination is enough.
ZS. I have understood why the history was scrolling - it was because of Sleep() in the loop. Took it out and everything went back to normal!
I hear you, that's right. It's just that I'm looking at the request in depth and breadth, what might it be for? To stop in visual testing mode at the moment of making a deal and display some information, it might be useful for the client's visibility as well. And if it's purely for development and debugging, then yes, it's redundant, the existing DebugBreak is enough.
And what prevents you from running in debug mode and shooting video? Before opening a position, put DebugBreak, make appropriate inscriptions and continue the test. Then cut out the appearance of ME in the frame and switch back... If you want to make clips, you must have at least some primitive video editing software. There are plenty of them on the internet, even online applications. Plus you can put DebugBreak as a condition of working in debug mode. In other modes there will be no stopping.
This trick does not work in MT5 unfortunately - when you exit a cycle, it instantly scrolls through the history for as many days ahead as the tester would have gone through in that time without looping. Sounds strange, and looks even stranger on a chart, I hope you get my point))
Debug mode is extremely inconvenient for testing strategies (not code). In MT4 you could implement in the visual tester scrolling +1 bar, +1 tick, etc., as much as imagination is enough.
SZZ. I have understood why the history was scrolling - it was because of Sleep() in the loop. Removed it and everything is in place!
Maybe you put a slip in the loop there?
You can't putSleep in a loop, it really flips the ticks in mt5.
But a normal loop works the way you want it to.
Been using this trick for 4 years
More features are likely to be included soon:
Why SQLite and not some specialised time series database with compression support and other goodies?
They are much better suited to the field.
Why SQLite and not some specialised database for time series, with compression support and other goodies?
They are much better suited to the field.
Because it is a pure integrated solution for its own needs, including agent-based operation. The next release will integrate databases directly into the editor and new functions for massive operations.
And working with external databases can also be organised through a DLL.
For those testing, especially on broker history, the "exclude repetitive ticks" feature would be very useful (e.g. make it next to "profit in pips to speed up calculations")
On one popular broker I found that 8mln ticks out of 13mln per month are repetitive! Thus, we can significantly increase the speed of testing for purchased EAs or those that do not have such a program filter.
I also ask to make it possible to select more column parameters on the optimization results page. For example, I want to see the drawdown in the deposit currency during optimization with a fixed lot value, but it is impossible to select it - onTester is occupied by another parameter.
For those testing, especially on broker history, the "exclude repetitive ticks" feature would be very useful (e.g. make it next to "profit in pips to speed up calculations")
On one popular broker I found that 8mln ticks out of 13mln per month are repetitive! This can increase the speed of testing for purchased EAs or those that do not have such a program filter.
It can be done with custom symbols. But this setting is in TDS, as well as many others that would be useful in the regular Tester.