Logic Bug In BarsRequired vs. MinBarsRequired

[ChuckAllen]

Anyone would think that MinBarsRequired...means the Minimum Bars Required.
Nothing should basically be done until the MinBarsRequired is met!
There is NO parameter in the Optimize Param box to set the BarsRequired instead of/ or in addition to the MinBars Required.

If we set a value that says Minimum Bars Required in the param box, it should automatically set any other hidden variable to that value. Either that, or in the NT HIDDEN code (NOT IN EVERY USER'S CODE) should change everybody's generated code to reflect the Min Bars Required.

We should not have to add special code that seems like it should already exist in the skeleton logic of NT.

If there is some special reason for 2 ways to seemingly set the same value, please let us know.

[NinjaTrader_JoshP]

MinBarsRequired is not a supported property. The only supported property is BarsRequired. The UI parameter item shown as "Min. bars required" is the exposed UI parameter for BarsRequired. You should never be using MinBarsRequired.

[ChuckAllen]

Reply

Duh! No kidding. Please read the screen dump and supporting text.
Everything is Exactly what you just said.

I set the MinBarsRequired in the GUI, and the BarsRequired in the code.
That's why I said that if the MinBarsRequired does nothing, and you need
the BarsRequired...it should be in the GUI.

It still did not work! The chart and indicator values are still way off.

[NinjaTrader_JoshP]

As discussed in my previous post "Min. bars required" is the same thing as BarsRequired in code. It is the exposed UI parameter for BarsRequired.

Whatever you set in the UI takes precedence. Please review all of my posts in your other threads. This is working as expected and there is no bug.

[ChuckAllen]

Anybody every duplicate/acknowledge as a bug?

Did anyone ever duplicate the reported/documented problem and acknowledge it as a problem?

[NinjaTrader_Ray]

Hi ChuckAllen,

This is not a bug and is working as expected.