Your topic has been moved to the section: Expert Advisors and Automated Trading
Please consider which section is most appropriate — https://www.mql5.com/en/forum/172166/page6#comment_49114893
Please consider which section is most appropriate — https://www.mql5.com/en/forum/172166/page6#comment_49114893
d00lar: now processed is WRONG / have no mining to test this - then i return `init failed` - so it does not need to run this test and waste time on it
You should be returning parameters incorrect, not failed. OnInit - Event Handling - MQL5 Reference - Reference on algorithmic/automated trading language for MetaTrader 5
William Roeder #:
You should be returning parameters incorrect, not failed. OnInit - Event Handling - MQL5 Reference - Reference on algorithmic/automated trading language for MetaTrader 5
You should be returning parameters incorrect, not failed. OnInit - Event Handling - MQL5 Reference - Reference on algorithmic/automated trading language for MetaTrader 5
i see thx i will change that
but this not change anything - from my point of view failed is also done / this should not affect time calc..?
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
hello
i think this is a bug and should be fixed - where i can report this?
if i do some large FULL optimalization that will take several hours - lets say 77h like on screen in attachment
294784 paasses to do
but in some cases (+- 30%) - i KNOWN that this parameter set that is now processed is WRONG / have no mining to test this - then i return `init failed` - so it does not need to run this test and waste time on it
so after 25h - it says that it is doing test no 96328
BUT IN REALITY AS ON OTHER SCREEN PART it is doing test no 127930 /126982 etc
so almost 30000 more tests are done than the counting here at the bottom - this are this init failed ones.
- IT IS NOT counting this that init failed as done - and probably BECAUSE of that - time calculation is WRONG
in real life - after next 24h - it will be saying that another +-24hours are still to go and then - in one sec - after really passing last ( 294784 test) - it will just simpy finish
i think that if this init-failed ones would be also counted as 'done' then time calculation probably would be a lot more accurate ?
please consider this issue
best regards