The tester opens deals for 2009 (a lot), but does not want to open deals for 2010. If you take a boundary period, it works up to the end of 2010, and then it does not.
The tester opens deals for 2009 (a lot), but does not want to open deals for 2010. If you take a boundary period, it works up to the end of 2010, and then it does not.
????
I wish I could count to the end of 2010 at least, it's all over yesterday !
Hooray, now the tester works at a normal speed, if you remove the limitation on the number of optimised parameters, then maybe I will think whether to switch to the tester from MetaQuotes Software Corp :)
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
The tester opens deals for 2009 (a lot), but does not want to open deals for 2010. If you take a boundary period, it works up to the end of 2010, and then it does not.
????
The tester opens deals for 2009 (a lot), but does not want to open deals for 2010. If you take a boundary period, it works up to the end of 2010, and then it does not.
????
I wish I could at least count to the end of 2010, it's all over yesterday !
Yeah, sorry about that. What's the point?
Question to the tester developers :
Does pressing the sort button during optimization affect the logic of the genetic algorithm?
Who knows what's in your code? What does it say in the log? Have you checked it?
Question to the tester developers :
Does pressing the sort button during optimization affect the logic of the genetic algorithm?
Of course it won't. Firstly, MT5 in the tester counts swaps and floating spreads. In MT4 this is not the case.
No errors, and the rest - I'm not an expert but everything seems to be fine (loaded, synchronised, etc.)