Strategy tester. - page 7

New comment
 
Renat - to help the cause.
Difference of run with the same Expert Advisor in MT175 and MT176 from 1.1.2004 to CurTime()


Number of open orders in MT175 = 2902; in MT176 = 20

Unclear multiple (>10000) errors in logs in MT176 (none in MT175)
like
<br / translate="no">
10:06:19 2004.01.13 09:56 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=5
10:06:19 2004.01.13 13:38 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=6
10:06:19 2004.01.13 14:35 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=7
10:06:19 2004.01.13 15:29 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=8
10:06:19 2004.01.13 17:05 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=9
10:06:19 2004.01.13 21:50 exp4: Error opening order : 2 ; common error tip_signal= 3,* signal= -1, kol_zdelok=10
10:06:19 2004.01.14 09:01 Tester: take profit #4 at 1.2708 (1.2706 / 1.2710)
10:06:19 2004.01.14 09:05 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:06 Tester: take profit #3 at 1.2698 (1.2688 / 1.2692)
10:06:19 2004.01.14 09:07 Tester: take profit #3 at 1.2698 (1.2687 / 1.2691)
10:06:19 2004.01.14 09:08 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:09 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:10 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)
10:06:19 2004.01.14 09:11 Tester: take profit #3 at 1.2698 (1.2689 / 1.2693)
10:06:19 2004.01.14 09:12 Tester: take profit #3 at 1.2698 (1.2689 / 1.2693)
10:06:19 2004.01.14 09:13 Tester: take profit #3 at 1.2698 (1.2686 / 1.2690)
10:06:19 2004.01.14 09:14 Tester: take profit #3 at 1.2698 (1.2685 / 1.2689)
10:06:19 2004.01.14 09:15 Tester: take profit #3 at 1.2698 (1.2688 / 1.2692)
10:06:19 2004.01.14 09:16 Tester: take profit #3 at 1.2698 (1.2691 / 1.2695)
10:06:19 2004.01.14 09:17 Tester: take profit #3 at 1.2698 (1.2693 / 1.2697)


Conclusion: You have messed up something there in 176, we will have to use 175 for now.
Good luck.
 
giv, download the corrected version of the 176 build from our website and try running the EA again.
 
giv, download the corrected version 176 build from our website and try running the EA again.

OK. It works.
 
As far as I understand, the Print command does not work when testing strategies. Can you make a window for outputting information from Expert Advisor? Or at least automatically dump it into a log file?
It is rather boring to prescribe an Expert Advisor to see what it outputs, to say the least.
 
As far as I understand, the Print command does not work when testing strategies. Can you make a window for outputting information from Expert Advisor? Or at least automatically print it to the log? <br / translate="no"> I don't want to bother prescribing the Expert Advisor to see what it displays, to say the least.

Print function doesn't work only during optimization. It works during simple testing.
 
<br / translate="no"> the Print function only fails during optimisation. during simple testing it works

Can you clear the log?
When you run the Expert Advisor several times, so much rubbish accumulates there :(
I mean in the tester.
 
Can you do a log cleanup? <br / translate="no"> When you run the EA several times, so much rubbish accumulates there :(
I mean in the tester.

have to think about it
 
Насколько я понимаю команда Print не работает при тестировани стратегий. Может вы сделаете окно для вывода инфы из эксперта? Или хотя бы автоматом будете скидывать это в лог?
Преписывать эксперт для просмотра что он там выводит несколько влом, если не сказать больше.

The Print function only fails during optimisation, but works during simple testing.


Yeah, it didn't seem to work to me though. Print() works in init(), but not in start()
 
Or rather, it works kind of thoughtfully. Sometimes it works. Very sometimes :)
For instance, out of 6-8 Print() only 1 works. The rest never get into the log during tests. Without optimization, of course.
 
Or rather, it works kind of thoughtfully. Sometimes it works. Very sometimes :) <br/ translate="no"> For instance, out of 6-8 Print() only 1 works. And the rest of them never get into the log during testing. Without optimization, of course.

Open the corresponding log file in the log file using the context menu and see if it was printed or not. The data are printed to the log tab asynchronously, on a timer so as not to slow down the tester, therefore you can lose data in the tab (and not in the log, i.e. not in the log itself).
1234567891011
New comment