).Report if problems of different sort pop out.
]]> ).Report if problems of different sort pop out.
]]>
I have removed this indicator (Bar Type) from the Active Indicators List to avoid this problem. As I understand it is not an external indicator from Repository, but it is a build in indicator.
Leon
]]>Footon, you can greatly improve the performance of this indicator.
Now, if we have 50000 bars and the indicator period is 500, it checks (50000-500)*500 = 24 750 000 times the signal conditions.
You can easily remove the loop-back cycle.
///
In that way you will calculate it with only 49 500 checks.
...
The error is division by zero. It looks like there are conditions where it happens. The solution is to check if the divisor is 0 prior to division.
same indicator same error again
What data do you use? Tell me timeframe and source of it.
]]>Now, if we have 50000 bars and the indicator period is 500, it checks (50000-500)*500 = 24 750 000 times the signal conditions.
You can easily remove the loop-back cycle.
Instead of:
for (int iBar = firstBar; iBar < Bars; iBar++)
{
for (int l = 1; l <= Period; l++)
{
if (Close[iBar-l] > Open[iBar-l])
countup++;
...
...
}You can calculate it with one pass with something like that:
for (int iBar = firstBar; iBar < Bars; iBar++)
{
if (Close[iBar-period] <= Open[iBar-period])
countup--;
if (Close[iBar] > Open[iBar])
countup++;
...
}In that way you will calculate it with only 49 500 checks.
...
The error is division by zero. It looks like there are conditions where it happens. The solution is to check if the divisor is 0 prior to division.
]]>