someone could tell me why the following code doesn’t work?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
oncecbidx=-1
onceorsi=-1
oncecrsi=-1
oncelrsi=-1
oncehrsi=-1
curr=rsi[period](close)
ifBarIndex=cbidxthen
crsi=curr
ifcurr>hrsithen
hrsi=curr
elsifcurr<lrsithen
lrsi=curr
endif
else
cbidx=BarIndex
orsi=curr
crsi=curr
hrsi=curr
lrsi=curr
endif
ifcrsi>orsithen
drawcandle(orsi,hrsi,lrsi,crsi)coloured(0,200,0)
else
drawcandle(orsi,hrsi,lrsi,crsi)coloured(200,0,0)
endif
RETURN20as"20",80as"80"
It was supposed to graph rsi as candlestick, instead it only graphs a single dash of current value. I didn’t expect it to work in already completed bars (because I imagine for that bars only ohlc are available), but I don’t understand why it doesn’t work in real-time bars.
ifBarIndex=cbidxthen// it is never -1 cause it starts with 0, so
rval=1// the plotted val will never be 1
else// but instead
rval=0// the plotted val will be 0
cbidx=BarIndex// and cbidx is set to the current BarIndex
endif// end of condition check
RETURNrval// condition examined, result found and plotted
As far as I see it, you have a condition which is checked and a result is found and plotted. There is nowhere something telling the program to repeat the condition check.
I totally agree with you during the first execution of the code; that body is from a dummy indicator I wrote to reproduce the issue. Being an indicator, I expect that body will be executed for every tick; from the second execution onward cbidx won’t never be -1, it will be most of the time equal to BarIndex (except during the first tick of a new bar). So, most of the time the result should be 1.
Being delcared as “once” (that from what I understood from doc is somewhat similar to “static” keyword in classical programming languages) the previous values of cbidx and rval should be kept.
I’m sorry to bother you (again) with this issue, but really I don’t understand the code execution logic behind an indicator. Another example:
<pre class=”lang:probuilder decode:true “>once cbidx=0
once a=0
a = BarIndex-cbidx
cbidx = BarIndex
return a
1
2
3
4
5
6
7
oncecbidx=0
oncea=0
a=BarIndex-cbidx
cbidx=BarIndex
returna
The returned value, a, is always 1.
I really don’t understand how is that possible!!!! The only way for “a” to be always 1 is that my code is executed only when a new bar is formed (more specifically, on the first tick of every new bar). But looking at other indicators I can see their values changing every tick, so the indicator has to be executed every tick. I checked the official doc again but it’s quite useless.
Live calculation of an indicator for an on-going candle is at every tick, so yes a=1. The only way I would understand the question and why you think a=1 is impossible would be in case you had a different understanding for “once” of what it really does, and would be expecting a to remain =0?
If that’s the case, what “once a=0” does is to perform a=0 just once at first candle, it’s a line not read at following candles, and it doesn’t prevent either other calculations to be made for “a” in the code. It means “read this line just once at the beginning of the history”, it doesn’t mean “this is the value of a once and for all”.
If this wasn’t the problem, sorry I completely misunderstood the question…
I’m sorry but english not being my language maybe I can’t explain my thoughts clearly.
I’ll try one more attempt; lets see these two lines of code:
1
2
a=BarIndex-cbidx
cbidx=BarIndex
From my understanding, BarIndex is an increasing counter counting the bars processed in the graph. If you agree with that, so the value of BarIndex will change every first tick of a new bar; said in another way, all the ticks of the same bar will have the same value of BarIndex.
If what I just said is true, so the variable “a” should always be 0, except for every first tick of a new bar.
Suppose that the code is evaluating the last tick of bar 1000; the variables are
a = 1000-1000 = 0
cbidx = 1000
The next tick will be the first tick of bar 1001; so the variables will be
a = 1001 – 1000 = 1
cbidx = 1001
Again, the second tick of bar 1001; the variables will be
ok I think I see what you mean, it implies you consider cbidx would change value at first tick and keep it in memory for second tick of same bar, but what the code does is reevaluate at each tick what the latest close price mean for all variable values compared with previous bar’s values, not with previous tick values of current bar… so in other words, if cbidx is calculated on a tick which is not the last of the candle, then its calculation is “forgotten” for this tick and “remade” at next tick starting again from values at close of previous candle, and only calculation of last tick of a candle is then kept for calculations of next candle
Values that can change from tick to tick within the same bar are stored in platform reserved keywords, like high or low. But for a user-created variable inside a probuilder personal code, within a given timeframe, I am not aware of any way to store in memory all the diffrenent values such a variable went through at ticks before the last one inside a same candle. Even using a drawcandle command to display the range an indicator value would have to happen by calculation at last tick from price open,high,low,close of cnadle rather than intermediate-tick memory storing… Nicolas might correct me when he’s back if I’m wrong…
.
.
