Arrays related bugs

LucasBest · 2024-12-28T09:45:45+00:00

Below are 2 strange bugs I have encountered while using Arrays extensively : 1 – Using the instruction “Lastset” in order to fill the arrays possibly resulting in errors. ProrealTime will not send an error message but you may see strange things on the screen… $MyTab[Lastset($MyTab)+1] = value //should be avoid //////////////////////////////// once MyTabIndex = -1 ... MyTabIndex = MyTabIndex +1 $MyTab[MyTabIndex] = value //More safe to avoid strange bugs // MyTabIndex is last index of the array $MyTab defined 2 – Sometimes you will get an error message from ProrealTime saying that the code is trying to reach an index of an array that is not strictly positive integer… And that is weird as i use one variable pointing to lastset element for each array i use… (like mentioned above) First, i mention that i always have this condition in my code : If MyArrayIndex >= 0 then ... Drawtext($Myarray[MyArrayIndex], barindex, high+10) //like this it may lead to an error message from ProrealTime ... endif I always add this condition before trying to reach any value of the array, because of course you don’t know if it had been already filled or not… But even with this condition before trying to get a value of the array, you may have the error message from Prorealcode, which is really strange! The only way i found to solve this problem is to use an other variable just before accessing to the array, like this below : If MyArrayIndex >= 0 then ... Mytemporaryvariable = MyArrayIndex Drawtext($Myarray[Mytemporaryvariable], barindex, high+10) //like this i have no error message ... endif Have you also experiences such errors/bugs with arrays ?

Viewing 4 posts - 16 through 19 (of 19 total)

← 1 2

Author

Posts

12/30/2024 at 12:47 PM #241950 quote

LucasBest

Participant

Senior

Look, even if i add an other condition to check if the first array have been updated, it leads to the same error even if i check if the index of the first array is filled with “isset” instruction… That means that the array is temporarly updated then deleted to come back to previous situation according to the real close at the end of the bar!
=> Thus the only way to prevent this bug if to send the variable index into an other variable (temp) which then will occurs only at the end of the bar, preventing the code to reach an index of the first array that have not been permanently filled yet.

Once RSILen = 14
Once prd = 1
Once pBcTi = -1
Once pBmTi = -1

src = RSI[RSILen](close)

If src[prd] = lowest[2*prd+1](src) then
pBcTi=pBcTi+1
$pBcT[pBcTi]= Barindex-1

if pBcTi > 2 and isset($pBcT[pBcTi]) then
if src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi-2]] and src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi]] then
pBmTi=pBmTi+1
$pBmT[pBmTi]= $pBcT[pBcTi-1]
drawpoint($pBcT[pBcTi-1],src[barindex-$pBcT[pBcTi-1]],3) coloured("red",100)
endif
endif
endif

Return src

12/30/2024 at 12:51 PM #241951 quote

LucasBest

Participant

Senior

I tried also using Lastset instruction… It does not solve the problem either!

Once RSILen = 14
Once prd = 1
Once pBcTi = -1
Once pBmTi = -1

src = RSI[RSILen](close)

If src[prd] = lowest[2*prd+1](src) then
pBcTi=pBcTi+1
$pBcT[pBcTi]= Barindex-1

if lastset($pBcT) > 2 then
if src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi-2]] and src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi]] then
pBmTi=pBmTi+1
$pBmT[pBmTi]= $pBcT[pBcTi-1]
drawpoint($pBcT[pBcTi-1],src[barindex-$pBcT[pBcTi-1]],3) coloured("red",100)
endif
endif
endif

Return src

12/30/2024 at 1:05 PM #241952 quote

LucasBest

Participant

Senior

But things get even stranger here below…

Once RSILen = 14
Once prd = 1
Once pBcTi = -1
Once pBmTi = -1

src = RSI[RSILen](close)

If src[prd] = lowest[2*prd+1](src) then
pBcTi=pBcTi+1
$pBcT[pBcTi]= Barindex-1
temp = pBcTi
if temp > 2 then
if src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi-2]] and src[barindex-$pBcT[pBcTi-1]] <= src[barindex-$pBcT[pBcTi]] then
pBmTi=pBmTi+1
$pBmT[pBmTi]= $pBcT[pBcTi-1]
drawpoint($pBcT[pBcTi-1],src[barindex-$pBcT[pBcTi-1]],3) coloured("red",100)
endif
endif
endif

Return src

Can you explain that ? 🙂

01/04/2025 at 6:53 PM #242162 quote

LucasBest

Participant

Senior

Will we have something like PineScript instructions concerning bar state ?

barstate.isconfirmed for exmple? Because using multiple arrays, with arrays that are updated by other arrays lead to strange results…

https://www.tradingview.com/pine-script-docs/concepts/bar-states/#introduction

Thanks