return(INIT_AGENT_NOT_SUITABLE);
But if I put it in the EA which I am having trouble with there is still no error and no passes so that tells me the process is crashing even before the oninit is called.
Suspects:
too many inputs, too many arrays. too many include files/too many lines of code.
If I put this line in the working EA then I get the appropriate error and I still get passes with 0 trades:
But if I put it in the EA which I am having trouble with there is still no error and no passes so that tells me the process is crashing even before the oninit is called.
Suspects:
too many inputs, too many arrays. too many include files/too many lines of code.
Do you have any statement in your code to stop the tester ? TesterStop() or even ExpertRemove()
If yes you need to investigate why it's triggered. If not, it's probably something else in your code (which trigger possibly due to an MT5 bug), as you have the problem only with this EA.
Do you have any statement in your code to stop the tester ? TesterStop() or even ExpertRemove()
If yes you need to investigate why it's triggered. If not, it's probably something else in your code (which trigger possibly due to an MT5 bug), as you have the problem only with this EA.
Hi Alain, thanks for your reply.
I do not have TesterStop() or ExpertRemove() in my code anywhere nor in any of the include files.
Yes probably something else in my code since it is only this one EA.
Is there something more I should do to report this bug? I could only find a general recommendation to post bugs in the forum.
Hi Alain, thanks for your reply.
I do not have TesterStop() or ExpertRemove() in my code anywhere nor in any of the include files.
Yes probably something else in my code since it is only this one EA.
Is there something more I should do to report this bug? I could only find a general recommendation to post bugs in the forum.
Maybe you could also check if you have the same problem with an other broker.
To report the bug, you will need to provide code to reproduce the issue, and a small explanation how to reproduce it. If you do it I will add your bug to my topic.
If you can't post the code publicly, please contact me in private and I will explain you how to proceed.
- 2021.04.23
- www.mql5.com
Maybe you could also check if you have the same problem with an other broker.
To report the bug, you will need to provide code to reproduce the issue, and a small explanation how to reproduce it. If you do it I will add your bug to my topic.
If you can't post the code publicly, please contact me in private and I will explain you how to proceed.
OK sure in the meantime I created my first python script. It seems to work. Iterates through all the symbols one at a time and makes a test and a report.
import os mt5inidir = r'D:\test\myini.ini' directory = r'C:\Users\user\AppData\Roaming\MetaQuotes\Terminal\A6260AEED2D6E7E5976B5FCB754\bases\Default\history' mt5dir = r'C:\PROGRA~1\HIOL~1\terminal64.exe /config:D:\test\myini.ini' for entry in os.scandir(directory): if (entry.is_dir()): print(entry.name) myini = '''[Tester]\nExpert=c7v3\c7v3.ex5\nShutdownTerminal=1\nModel=1\nReport=''' + entry.name + '''\nSymbol='''+entry.name print(myini) f = open(mt5inidir, "w") f.write(myini) f.close() print(os.system(mt5dir))
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Each of the three symbols works fine when I run them one at a time with optimization disabled. A regular genetic optimization also works fine. I've tried m1 ohlc. I've tried short/longer sample size. I've tried other symbols. I've rebooted. I've cleared all the data from the bases directory and started from scratch.
EDIT:
This is what's in the /tester/logs
Other EA work fine it is just this one EA.