Question about CalculationMode.Ticks

[Brevo]

Hello,

I am trying to code a strategy for MNQ.

I have a variable takeProfit. I set it to 60:

takeProfit = 60;

I then set a profit target with CalculationMode.Ticks:

SetProfitTarget(CalculationMode.Ticks, takeProfit);

If what I think is correct this strategy would close when the price is 60 ticks in profit. That would be $120 for MNQ since it's $2 per tick.

But today in simulation it ran up to $511+

I tried to google this and haven't found an answer. Please help me understand this. Thank you.

[NinjaTrader_Jesse]

Hello Brevo,

From the image that appears to be the positions tab which shows the currently unrealized PnL. Are you able to see in the orders tab or on a chart what the profit target price was set to? The positions tab pnl is based on the average entry price and current market price which gives you the unrealized PnL from the point of entry.

[Brevo]

Nothing is set for the profit target in the order tab. Should that happened automatically? I didn't use the chart. The order tab screenshot is attached.

[NinjaTrader_Jesse]

Hello Brevo,

The target should automatically be submitted when the entry fills, where did you put that code inside your script? The reason for the higher than expected pnl would be due to no target being active and that is just how much unrealized pnl the position currently has.

[Brevo]

I added the code in OnStateChange():

else if (State == State.Configure)
{
SetProfitTarget(CalculationMode.Ticks, takeProfit);
SetStopLoss(CalculationMode.Ticks, stopLoss);
}

[NinjaTrader_Jesse]

Hello Brevo,

That should be the correct placement. Did you compile the script and then remove/re apply it after making that change?

[Brevo]

The code has been there since the beginning and yes has been compiled and backtested. Recently added to a simulation account.

[NinjaTrader_Jesse]

Hello Brevo,

In that case I would suggest using TraceOrders and then re test the strategy in the same use case during realtime. If the order was not submitted for some reason traceorders should be able to let you know why that was.

https://ninjatrader.com/support/helpGuides/nt8/traceorders2.htm

That information will go to the NinjaScript output window so you will need to have the output open when testing.