I have this problem too
Same here. Have you found a solution?
In build 2006 and build 2007 I am seeing similar issues with parameter transfer from the Optimisation Results tab to the Inputs tab, although 2007 seems better.
With 2006, fields using enumerated types, such as MA Smoothing Methods and Applied Price are bad at being copied across. I have not tested this in 2007.
Comparing how build 1940 used to behave with builds 2006 / 2007, what I have also noticed, and this is a particularly bad problem, is the vast difference in the 'Result' value for each parameter combination in an optimisation run, and the result then shown when then invoking a single test using the same optimised parameters.
So for example a given line in the optimisation results tab might say 245 trades, loss of 176.2, and when running those parameters as a single test to see the equity curve, the end result (confirmed from the Back Test Report) was 284 trades (another +39) and loss of -822.62 (another -646.42).
I tried this without cloud optimisation, but with and without local network tester agents, using 'Every tick based on real ticks' and connected to a live account for data.
This difference in the optimisation results means I don't know what to trust - the optimisation results, or the single run result
Without trust in the back tests, I can't proceed with testing and development.
I have even gone to test the demo applications that come with MT5, for example the Moving Averages EA and the ExpertMAMA EA. I have noticed that the difference in the results tab versus single run for Moving Averages was not much, but the difference in results tab vs single run result for Wizard / Standard Library based ExpertMAMA was much worse. So I am concerned that the Standard Library is exposing some calculation bugs.
In build 2006 and build 2007 I am seeing similar issues with parameter transfer from the Optimisation Results tab to the Inputs tab, although 2007 seems better.
With 2006, fields using enumerated types, such as MA Smoothing Methods and Applied Price are bad at being copied across. I have not tested this in 2007.
Comparing how build 1940 used to behave with builds 2006 / 2007, what I have also noticed, and this is a particularly bad problem, is the vast difference in the 'Result' value for each parameter combination in an optimisation run, and the result then shown when then invoking a single test using the same optimised parameters.
So for example a given line in the optimisation results tab might say 245 trades, loss of 176.2, and when running those parameters as a single test to see the equity curve, the end result (confirmed from the Back Test Report) was 284 trades (another +39) and loss of -822.62 (another -646.42).
I tried this without cloud optimisation, but with and without local network tester agents, using 'Every tick based on real ticks' and connected to a live account for data.
This difference in the optimisation results means I don't know what to trust - the optimisation results, or the single run result
Without trust in the back tests, I can't proceed with testing and development.
I have even gone to test the demo applications that come with MT5, for example the Moving Averages EA and the ExpertMAMA EA. I have noticed that the difference in the results tab versus single run for Moving Averages was not much, but the difference in results tab vs single run result for Wizard / Standard Library based ExpertMAMA was much worse. So I am concerned that the Standard Library is exposing some calculation bugs.
See reproducible case and report here https://www.mql5.com/en/forum/305758
- 2019.03.05
- www.mql5.com
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
2 things are broken:
* After optimization the StrategyTester resets all optimization parameters to default settings. (Totally unacceptable, unworkable)
* Selecting the 'Run Single test' from the 'Optimization results' tab does NOT copy the settings to the input tab. (Previous versions always did.)
Please fix asap.