Enter Long When Bar Close Low Cause Trail Stops To Be Amended Immediately

[Edward Kunafi]

Hello Support,

During testing of strategy I found the following behaviour. I am using Range bar with period of 5. Strategy call EnterLong, when bar close low. After order filled NT submits target and trail stop orders correctly as per my settings. The trail stop in this case being 10 ticks away from entry. Immediately after that, NT shows amended trail stops, the stops being moved 5 ticks towards entry price. Is this correct behaviour? Should NT Not skip first amendment? This is not a good behaviour.

Is there anyway to workaround this, other than adding stop ticks setting by the same amount?

Please see attached capture.

Thanks.

Best regards,

Edward Kunafi.

[NinjaTrader_Bertrand]

Hi Edward, it would amend the order whenever price would dictate it - if you wish to wait a bar after entry this could be achieved via a check with BarsSinceEntry().

http://www.ninjatrader.com/support/helpGuides/nt7/barssinceentry.htm

[Edward Kunafi]

Hello Bertrand,

Thanks for the reply. Interesting, but the example is too simple to be useful.
Can you enlighten me as to how I can use the BarsSinceEntry to affect behaviour of NT TrailStop?

Thanks.

Best Regards,
Edward K.

[NinjaTrader_Bertrand]

Edward, you would the use to start trailing only after a bar has passed by sending the Set command then and not automatically attaching it via the static Initialize() call.

[Edward Kunafi]

Hello Bertrand,

How do I remove a SetTrailStop settings that is already been defined (at Initialize or other places) before?

Thanks.

Best Regards,
Edward K.

[NinjaTrader_Bertrand]

You could unfortunately not remove or unSet() them. You could only call them again to adjust the order. More flexibility here would be provided by using the more advanced Exit() methods, here an IOrder return is given so CancelOrder() could be used.

[Edward Kunafi]

Hello Bertrand,

The first option to call it again is kind of difficult, because I have already finish with the bar. Unless I introduce, secondary bar. Probably it is easier to just add BarsPeriod to the stop setting, prior to calling the EnterLong. The second option with more flexibility would mean I handle the trailing myself, and send appropriate Exit where I want it.

Thanks.

Best regards,
Edward K.

[Edward Kunafi]

Hello Bertrand,

But seriously, the current bar close trigger the signal, generate the position, so the current bar is history, prior to the position, so it should not affect behaviour of the trail stop. It is kind of inconsistent to say mildly.
I would suggest you bring it up to development team to fix it for the next release. Would be glad to hear favourable outcome of this. Then I can roll back my own fix.

Thanks.

Best regards,
Edward K.

[NinjaTrader_Bertrand]

Thanks for the valuable feedback Edward, this is unfortunately a known limitation of the SetTrailStop(). I have added your vote for an enhancement though to our product management feedback tracking lists.