How to modify and retest an ATM strategy

[NinjaTrader_Christian]

Hi cassb !

Please try again with:
Swing(5).SwingHigh[5]

This is true, if 5 bars ago a swing occured. A swing high (low) is defined as a swing, if 'strength' bar before and after the candidate are lower (higher) then the actual value. Thus the value is always false for barsBack < strength.

Kind regards,
Christian

[cassb]

Hi cassb !

Please try again with:
Swing(5).SwingHigh[5]

This is true, if 5 bars ago a swing occured. A swing high (low) is defined as a swing, if 'strength' bar before and after the candidate are lower (higher) then the actual value. Thus the value is always false for barsBack < strength.

Kind regards,
Christian

Christian, you are a genius -- that worked beautifully! Now I can get rich with my strategy. haha

Bryan

[KBJ]

Documentation?

According to the Help Guide a zero value is returned under the following conditions.

* A return value of 0 (zero) will be returned if the CurrentBar is less than the "strength" value or a swing pivot has not yet been found.

Since you have this in red and people are still having problems with it, how about adding this example of "what not to do" into the help, too?

For example,

"Swing(5).SwingHigh[0]" will [B][COLOR=Red]always [/COLOR][/B]return zero.  

Please use "Swing(5).SwingHigh[5]" instead.

[cassb]

Or, what Christian said: "...the value is always false (or 0) for barsBack < strength." I guess I didn't connect the [0] part of the call with "bars back." I thought that since I want to know with the current bar whether a new swing high has occurred, that I would have to put 0 in there. Maybe it's just a confusing indicator because it's really measuring something <strength> bars ago but you don't know if it's true or false until <strength> bars pass.

[KBJ]

More Documentation?

Yes, it would be nice if all of this were spelled out in the Help file.

Of course, then I guess we would not have the excuse to exchange communications like this, but, oh well, you can't have everything.