the expert advisor is written, tested, everything seems to be fine, but!
It’s scary to use a large amount of money for it, I would like to provide for all sorts of unforeseen situations in the market that happen.
For example: gap, slippage, all sorts of errors.
Please advise what situations are possible and, if possible, how to protect it in the code?
nektomk
there is also a funny protection – all takeprofits must be virtual, although they seem to be limited. That is, to be worked out on the terminal side.
this is why you need a fast response and speed of work
Servers in controversial situations (geps, spread jumps, sometimes slippage/phase-moons) take will not be issued in your favor.
mt_linux_wine_haltura
I don’t see the point in explaining myself to a boorish, superficial person. You either speak to the point, or you are silent. So You believe you’ll be able
Should I explain how many cycles it takes for n functions to be executed in the Expert Advisor? Well, in general, what is enough attention paid to the mql educational literature ?
nektomk
what just happened right from Wednesday ? and there was leisure and buy and check..
hint: profiles are available for everyone to read – you are here 4 days from the date of registration 🙂
mt_linux_wine_haltura
The topic is absolutely relevant. It is unclear where the skepticism of some of the inhabitants of the forum. I still do not see any steps in the direction of
compiling algorithms, with checks and greedy algorithms. At the same time, the code is even disgusting for money, and I have seen a lot of purchased prog.
apparently, no one cares about greed and network load at all, and even more so about checks. And even there is no understanding that it needs to be done.
The help is disgusting, the mql lessons are only from one publisher, and of very poor quality. The main thing is to inflate your cheeks more and play the
guru-cynic. And in recent years, not a single step in the direction of drawing up any normal lessons or manuals is visible. And they would
be useful not only for beginners, but also for crowds of experienced *****coders.
b
there can be a lot of situations. Slippage is set as a parameter when opening a position, the spread can be analyzed before opening
the position of the gap too, just like everything else. Just in case, you can add minimum thresholds as a filter:
This is so as not to drain everything if something goes wrong.
net
Then put return after OnTimer()
nektomk
geps, slips and spread dances should be taken into account in the owl algorithm and the libraries used.
and besides, do not keep on the account the amounts more required in the work of the adviser (that is, it is not about signals and pamm – if for yourself)
Focus on the minimum value of freemargin for a reasonable (for comfortable deposits/withdrawals) period.
sysmart
Brilliant! I hope you’ve run out of ideas!
trendhunter
Just after onTick (), insert return and you’ll be safe