BIP for Exit conditions..

[zachj]

For the following code below for the exit conditions I'm using Index 2, do I need the BIP ==2 in there like I have below, or seeing I designated Highs with Highs[2] already will I not need the BIP in there?

if(Position.MarketPosition == MarketPosition.Long
&& (BarsInProgress == 2)
&& SMA(Highs[2], fast)[0] < SMA(Highs[2], slow)[1] -.75)

{
ExitLong(0, 1, "", "");
}

[NinjaTrader_Bertrand]

Hi zachj, you could change the Highs[2] to just High, since you are accessing those series in BIP == 2 context. You can remove the BIP context call as well, however that would change the event timing, so when you statement will be evaluated - currently with the BIP == 2 check in that would be when the second added series calls OnBarUpdate().

[zachj]

So you say this will change the event timing, what are the consequences of this? I'm still not quite clear. Is it more accurate to use BIP or just have the index worked right into the High ie Highs[2]?

[NinjaTrader_Bertrand]

Well, there's no right or wrong - it depends what you wish to do, on which bars update to act with your code. If you want to act on the BIP == 2 update > then this filter would need to be in the part of code.

If you just wish to access the data, then accessing High in BIP == 2 context would equal the access of Highs[2] without context.

[zachj]

To add some light, all I'm really trying to do is make it exit when a lower high is formed on Index 2. Is there any negatives or advantages to use one or the other in this case? Maybe one is slower/faster or something? I did notice it's changes my profit a little bit so there is definately a difference.

[NinjaTrader_Bertrand]

'To add some light, all I'm really trying to do is make it exit when a lower high is formed on Index 2'

Then I would work in BIP ==2. That's your index 2 update event...