Index was outside the bounds of the array

[Crassius]

Maybe we should have a Refactor My Code Sub Forum

Questions like this are not easily answered without the code, or with only code snippets. Ricam is answering the question, but with out demonstarting it by refactoring the code in question.. which was never posted... it's hard to get the point across.

[NinjaTrader_RyanM1]

Is it the equivalent (in a more sophisticated way) of the minimum bars required (backtest)?

Right, the strategy has built in handling for the first few bars with Minimum Bars Required. Indicators will need this custom coded. The following post can help with these techniques:

http://www.ninjatrader.com/support/forum/showthread.php?t=3170

[ch9090]

Thank you Crassius, I didn't want to bother the board members with my code but you're right. Next time I'll post it so it is clearer and thus easier to solve.

I need to do some furhter testing with the DMIndex as it seems to easily generate memory exception errors contrary to the RSI that works fine. Strange because the DMIndex is an upgraded RSI.

More in the next episode :-)

All the best, Chris

[j2496i]

Refactoring, and optimization for memory usage.

Maybe we should have a 'refactor my code' forum

Crassius - I think this would be a great idea. On a similar note - I have, so far, seen no discussion in these forums, into the optimization of code to improve memory usage - especially that which is non-linear...

I've recently developed a set of techniques to benchmark / query memory usage over time or iterations, and export the data to a spreadsheet for analysis and reporting. I find this extremely useful in optimizing my code and in isolating problematic sections, and I believe the importance of this is widely neglected when attempting to perform parametric cross-optimization.

I need to tidy up the code a little, but once I'm done I would be happy to post it here, and write a short article on this topic. Perhaps we could get a dedicated sticky?

I'm fairly busy right at the moment, so will likely be at some point next week.

J