Mountain chart type and OnBarUpdate...

[Mark--]

Hello,

In years past I created two indicators for use on a bar chart, worked fine.
I am starting a new indicator and began with a bar chart and all was/is well. The new indicator needs to to run on a mountain chart and when I tried to use the new indicator the fun stopped.

The chart has many "bars" or for the mountain chart, many close data points.
Version 8.0.26.1 64-bit
1 minute chart

double currentClose = Close[0];
double previousClose = Close[1];​

Error:

Error on calling 'OnBarUpdate' method on bar 0: You are accessing an index with a value that is invalid since it is out-of-range. I.E. accessing a series [barsAgo] with a value of 5 when there are only 4 bars on the chart.

The question, how to get the current and previous data point for the chart.

Ideas?

Thanks,

Mark

[NinjaTrader_ChelseaB]

Hello Mark,

You can ignore the chart style as this is not involved.

You are attempting to call Close[1], which is the close of the previous bar, on the very first bar.

If there is only one bar processed when CurrentBar is 0, you cannot call 1 bar ago. You have to wait until 2 bars are processed.

See the forum post below.

https://ninjatrader.com/support/forum/forum/ninjatrader-8/indicator-development/1046200-indicator-that-calculate-in-different-chartime?p=1048513#post1048513

[Mark--]

You are attempting to call Close[1], which is the close of the previous bar, on the very first bar.

Thanks for the response but as I wrote in the post "The chart has many "bars" or for the mountain chart, many close data points."

[NinjaTrader_ChelseaB]

Hello Mark,

The historical data starts processing with the first bar, when CurrentBar is 0.

After this it processes the next bar, CurrentBar is 1.

This continues through every bar on the chart.

[Mark--]

The historical data starts processing with the first bar, when CurrentBar is 0.
After this it processes the next bar, CurrentBar is 1.
This continues through every bar on the chart.

Thanks for the reply.

OK there is some confusion and it might be on my end.

With a bar chart.

Close[0] refers to the current bar.
Close[1] refers to previous bar

Only this code in OnBarUpdate, works without error in a bar chart:

Print("Bar 0 call");
double previousClose = Close[0];
Print("Bar 0: " + previousClose);

Print("Bar 1 call");
double currentClose = Close[1];
Print("Bar 1: " + currentClose);

Print("OnBarUpdate end");​

Here is the output:

Bar 0 call
Bar 0: 4041.25
Bar 1 call
Bar 1: 4039.5
OnBarUpdate end
Bar 0 call
Bar 0: 4041.25
Bar 1 call
Bar 1: 4039.5
OnBarUpdate end

The exact code in a mountain chart, output:

Bar 0 call
Bar 0: 3986.75
Bar 1 call
Indicator 'Dangle': Error on calling 'OnBarUpdate' method on bar 0: You are accessing an index with a value that is invalid since it is out-of-range. I.E. accessing a series [barsAgo] with a value of 5 when there are only 4 bars on the chart.

It seems OnBarUpdate for a mountain chart does not act the same as a "candlestick" chart.

What am I missing?

[NinjaTrader_ChelseaB]

Hello Mark,

If you add the code I suggested, does the error still occur?

[Mark--]

If you add the code I suggested, does the error still occur?

The:

if (CurrentBar < 1)
return;​

No it does not and thanks. It does not explain the issue. The "candlestick" chart does not need that code. Why? What else will be different?

The help for "CurrentBar" reads: "...the very first bar of the chart (left most bar) will be number 0 (zero)...", which is the opposite from Close[0], the active bar.

You wrote in the forum "The script will start from the far left of the chart at the very beginning where the CurrentBar will equal 0 and then start working to the right..." ...

Tell me you see the disconnect.

CurrentBar is numbered (older to newer) 0,1,2... newest is the highest number.
Close[] is numbered n,2,1,0, newest is lowest number.

Am I missing something?.

[NinjaTrader_ChelseaB]

Hello Mark,

Doing a test and printing Time[1], it does appear there is a phantom bar that is not on the chart.

I've reported this to our development.

[Mark--]

Doing a test and printing Time[1], it does appear there is a phantom bar that is not on the chart.I've reported this to our development.

OK, thanks, please post the results when available.