Indicator bars error "index was out of bounds of the array"

[koganam]

Hi Koganam, I am... it's logically the same as Joydeeps' earlier suggestion, that just checked them both individually with the ||.

In that case, you will need some Print() statements to isolate the line that is causing the error.

Here is the method that I use: ref: this post http://www.ninjatrader.com/support/f...gun#post245553 in this thread: http://www.ninjatrader.com/support/f...gun#post245458, which unsurprisingly is about that exact error.

[CSharpTrader]

I have visual studio... I'll turn there first, as annoying it can be to try to debug live indicators. I'm hoping Joydeep has additional insight, too. Print statements.... 80's debugging, the horror!! Thanks though.

[koganam]

I have visual studio... I'll turn there first, as annoying it can be to try to debug live indicators. I'm hoping Joydeep has additional insight, too. Print statements.... 80's debugging, the horror!! Thanks though.

I also use an IDE for final debugging. The shotgun Print() method simply shows me where to focus, instead of having multiple breakpoints to work through. I agree that it at first felt like stone age debugging, but I found that it saves me a whole lot of time, and allows me quick, laser-like focus. YMMV.

[CSharpTrader]

Joydeep, Koganam... I've got the error line.

3rd line down after if (BarsInProgress==0):

double keyPriceViolationLevelPriorDay = EMA(Closes[1],slowMA)[0]*1.0025;

Hope this helps. It's more specific but I'm still at a loss..

[koganam]

Joydeep, Koganam... I've got the error line.

3rd line down after if (BarsInProgress==0):

double keyPriceViolationLevelPriorDay = EMA(Closes[1],slowMA)[0]*1.0025;

Hope this helps. It's more specific but I'm still at a loss..

That is a different kettle of fish.

You are trying to access BarsArray[1] (i.e., Closes[1])from a tick triggered in BarsArray[0] (i.e., BarsInProgress 0). You may simply not have enough bars in BarsArray[1] at the time of access. You may want to double check the value of BarsArray[1] at the time of the access.

[CSharpTrader]

Btw I had been struggling to get it sync'd with VS2010 the whole time, thanks for the patience..

[CSharpTrader]

I thought that's what the original check CurrentBars[1] < slowMA + 12 addressed... don't we have enough bars if that returns true?

[koganam]

I thought that's what the original check CurrentBars[1] < slowMA + 12 addressed... don't we have enough bars if that returns true?

At first blush, yes, but you think that you have isolated the problem to that particular line, and you are getting a very specific error which seems to imply a certain explanation. If you care to post the entire code, I am willing to give it a run in my environment. You might also try restarting NT, just to be sure that you are not running into a .NET snafu.

I do not mean to be patronizing, but I have made this mistake so often myself, that I sometimes just ask to make sure: "Are you sure that you recompiled after you made the edit?"

[CSharpTrader]

No problem. Here it is in the latest form, below. Yup, recompiled (I too tend to make mistakes that are more absent- minded than higher- level). I attached the process to visual studio debug, and that line was the one that threw the out of bounds index error (despite passing the test in the initial check for # bars). I'll restart now per your suggestion. Fingers crossed. Thanks again.

protected override void OnBarUpdate()
        {
            for (int index = 0; index < BarsArray.Length; index++) 
            {
                if (CurrentBars[index] < (slowMA+12)) return;
            }
            
            
            if(BarsInProgress==0)
            {
                //Check for uptrend
                int uptrendCheckCount = 0;
                int countOfClosesOverSlowEma = 0;
                double keyPriceViolationLevelPriorDay = EMA(Closes[1],slowMA)[0]*1.0025;
                double keyPriceViolationLevelToday = EMA(Closes[1],slowMA)[0] + Math.Abs(EMA(Closes[1],slowMA)[0] - EMA(Closes[1],slowMA)[1]);
                
                for(int i=0;i<10;i++)
                {
                    if((EMA(Closes[1],fastMA)[i] >= EMA(Closes[1],medMA)[i]) && (EMA(Closes[1],medMA)[i] >= EMA(Closes[1],slowMA)[i]))
                    {
                        uptrendCheckCount++;
                    }
                    
                    if(Closes[1][i+1] >= EMA(Closes[1],slowMA)[i+1])
                    {
                        countOfClosesOverSlowEma++;
                    }
                }
                
                if((countOfClosesOverSlowEma==10)&&(uptrendCheckCount==10))
                {
                    if(Lows[1][0] <= keyPriceViolationLevelPriorDay)
                    {
                        if((Close[0] > Open[0])&&(Close[0] > keyPriceViolationLevelToday))
                        {
                            Plot0.Set(1);
                        }
                    }
                }
            }
        }

[koganam]

No problem. Here it is in the latest form, below. Yup, recompiled (I too tend to make mistakes that are more absent- minded than higher- level). I attached the process to visual studio debug, and that line was the one that threw the out of bounds index error (despite passing the test in the initial check for # bars). I'll restart now per your suggestion. Fingers crossed. Thanks again.

protected override void OnBarUpdate()
        {
            for (int index = 0; index < BarsArray.Length; index++) 
            {
                if (CurrentBars[index] < (slowMA+12)) return;
            }
 
 
            if(BarsInProgress==0)
            {
                //Check for uptrend
                int uptrendCheckCount = 0;
                int countOfClosesOverSlowEma = 0;
                double keyPriceViolationLevelPriorDay = EMA(Closes[1],slowMA)[0]*1.0025;
                double keyPriceViolationLevelToday = EMA(Closes[1],slowMA)[0] + Math.Abs(EMA(Closes[1],slowMA)[0] - EMA(Closes[1],slowMA)[1]);
 
                for(int i=0;i<10;i++)
                {
                    if((EMA(Closes[1],fastMA)[i] >= EMA(Closes[1],medMA)[i]) && (EMA(Closes[1],medMA)[i] >= EMA(Closes[1],slowMA)[i]))
                    {
                        uptrendCheckCount++;
                    }
 
                    if(Closes[1][i+1] >= EMA(Closes[1],slowMA)[i+1])
                    {
                        countOfClosesOverSlowEma++;
                    }
                }
 
                if((countOfClosesOverSlowEma==10)&&(uptrendCheckCount==10))
                {
                    if(Lows[1][0] <= keyPriceViolationLevelPriorDay)
                    {
                        if((Close[0] > Open[0])&&(Close[0] > keyPriceViolationLevelToday))
                        {
                            Plot0.Set(1);
                        }
                    }
                }
            }
        }

Not enough information. What other barSeries have you added, and with what parameters? You are referencing Closes[1]. Where did you define the additional barSeries?

[CSharpTrader]

*Gulp* It's me. As per my earlier comment on stupid mistakes (aren't they all?) I didn't have the 2nd data series added in the initialize method. Sorry. I had developed this as a strategy first, and just copied over OnBarUpdate(). Big waste of time.

We're running now, with a nice new issue. Getting alerts in the alerts window that don't match my conditions expressed in the code. The Plot0.Set(1) has a breakpoint, and the instrument that hits it doesn't generate an alert, but matches my conditions, and the one that does generate an alert, doesn't match the conditions, nor does it hit the breakpoint. Glad I love writing code.