Thanks to KapguHaJI,
V 1j is in post 1 and the IndiIntervalReadSeconds delay should work properly now.
The problem arose from the conversion of Simple Bob the single trader to SBB the multi-pair trader. Coders have seen my stuff so many times now that they know where to look for everything. Calls to indicators are all contained within a function called ReadIndicatorValues().
The delay works fine in a single trader because the function is only called once a tick. SBB calls ReadIndicatorValues() for every pair traded, so the delay was kicking in after the first pair and so the rest were not tested. That explains why those of us using the delay were not getting trades even though there was a signal. I would have worked this out eventually, but eventually might have been a while away and so KapguHaJI has saved us some pain.
For those of you who do not understand what the delay is all about, here is the explanation I send to people grumbling that the EA they paid me to code for their trading system involving 19 crap custom abortions slows their machine to a crawl:
The biggest problem with Crap Custom Abortions (known by the uninitiated as 'custom indicators') is one that lies at the heart of CrapTx. When an EA consults an indicator, the platform loads it into memory, then unloads it again once it has responded to the EA call. This takes time.
An indi has to do a lot of work up front when loaded onto a chart. Most of them are based on some sort of moving average, and the calculation has to be done over every bar on the chart. On subsequent ticks, the indi only has to update its calculation by updating the last x bars actually involved – the reason that, say, a moving average indi does not make your cpu emit blue smoke.
Custom indis typically consist of a number of calls to the regular indicators that ship with Empty4, and manipulate the information thus gleaned according to what the coder requires. An indicator such as AllAverages will make a number of calls to standard indicators. At each tick; each standard indi called by the custom indi is loaded, does all the up-front stuff, used, then unloaded. This takes a long time. Ridiculous, but that is how it works, and is the reason that custom indis such as AA and VQ slow your machine.
And then, we put the EA/Crap Custom Abortion on multiple charts.................................
Tommaso's indi is light-years ahead in standard of the kind of rubbish that most coders produce but it does rely on multiple calls to the usual indicators. We have it called to examine over 20 pairs twice a second - on several testing platforms. Once we have a basket open, we need the calculations done as often as possible, but do not need the indicators reading anything like as often. So, if your cpu appears to be struggling, then simply introduce a delay using IndiIntervalReadSeconds.
Read the effing manual, ok?
Afterprime is the official SHF broker. Read about them at https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?p=175790#p175790.
I still suffer from OCCD. Good thing, really.
Anyone here feeling generous? My paypal account is always in the market for a tiny donation. pianodoodler@hotmail.com is the account.
To see The Weekly Roundup of stuff you guys might have missed
Click here
My special thanks to Thomas (tomele) for all the incredible work he does here.
