Can't use pipes in Strategy Tester when using Network Farm Agents? - page 2
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
The last thing to check is a firewall.
firewall is setuped to let SMB-in (tcp 445).
Maybe the fact that metatester.exe runs in a service has different access rights ? Because the nodejs script from server2 can communicate with the pipe server(server1) with no issues.
Edit: I just tried starting the MetaTester service as the local user with admin priviledges instead of Local System and it failed with the same error code.
At this point, I just need to know if MT5 allows it, since it's not specified in the docs, I will probably need to contact support or post on the Russian forums...sigh
Thanks all for your help but I decided to go with the tester_file approach instead which seems to work a lot better for what I was trying to achieve.
I'm saving all json configs as a big binary file and it's pretty fast (file is around 700k).
Thanks all for your help but I decided to go with the tester_file approach instead which seems to work a lot better for what I was trying to achieve.
I'm saving all json configs as a big binary file and it's pretty fast (file is around 700k).
One important difference between tester_file and other communication approaches, that tester_file is static and one-way (will be sent "as is" to the agents at the beginning of optimization) and does not provide information exchange between agents (if you need probably this), whereas communications via external "transports" such as pipes can be dynamic and ad hoc.
One important difference between tester_file and other communication approaches, that tester_file is static and one-way (will be sent "as is" to the agents at the beginning of optimization) and does not provide information exchange between agents (if you need probably this), whereas communications via external "transports" such as pipes can be dynamic and ad hoc.
Yes I totally agree with you, I had high expectations from this setup, I may even use it later if I have the need but with the caveat that I will only be able to use local agents. For now, just having a big binary blob is fine for me. The only input that is optimized in my EA is the "configIndex", which enables each pass to know what to pick from the binary blob without parsing everything in memory.