So I’ve graphed the instrument values (see first screengrab). Now we can see the problem (finally!)
“Boll middle” is listed as 10,158
“Average[21]” is listed as 10,274
They are different values, but I’ve been working on the basis that Average[21] in code should refer to the black “Boll Middle” line. I’m using “Average[21]” because it is suggested to me as the code for the middle bollinger (as you can see from the other screengrab).
What is the code I should use to make sure I call up “Boll Middle” from Pro Order?
Check in your Bollinger Band indicator settings that everything is the same. Perhaps you have it set to use a simple average instead of an exponential average or maybe it is based on a different price to closing price?
Also consider using BOLLINGERUP and BOLLINGERDOWN and calculating the mid point between them.
It’s just the standard 21, 0.1 based on close (see screengrab). I’ve tried every combination in that box to try and return the value of 10,274, but none of them do. I can’t understand why indicator Average[21] is returning 10,274. There is also disparity between the EMoving Average 8 reading and my coded ExponentialAverage[8].
Is “Average[21](close)” the right syntax here? Or is there something else I should use?
You have something set wrong as your code uses a simple 21 period moving average of closing price. I have drawn it on my own chart four ways and they are all identical.
I tried to create a new chart from scratch and I got the same disparity. I then created a whole load of charts on different markets and there was no problem! It seems this is exclusive to the Bitcoin DFB chart (XBTUSD) on PRT linked to IG.
Thank you for your help. It is useful for me in future to know that I can graph instruments to double check unusual results.
Yes GRAPH and GRAPHONPRICE are very useful debugging tools.
I would send a technical report to PRT via your platform regarding the Bitcoin averaging problem if I was you (although it will go via IG so PRT may never receive it!)
On a similar theme to the above system, I’m trying to store met conditions for an entry that will only occur a number of bars after the first condition.
There are three entry rules for this system:
RSI goes above 80
RSI then drops below 75
RSI then rises above 80 again
I’ve coded it with similar principles to how you coded the two-rule code earlier in this thread, but I knew that it wouldn’t work because in code the first rule appears exactly the same as the third rule. When I use only the first two rules, it correctly enters when RSI drops below 75, so how do I store the first two conditions and then code a third rule to work after the first two? I’m aware that I can change the first and second rules to only act in previous bars with [5] or [6] for example, but this seems messy. Is there a clean way of creating three rules that act sequentially?
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
.
