Algo not working on Tick Chart

[elcowen]

The algo is suppose to be entering on 1 tick above previous high but its not anywhere close.


Thank you!
Ethan

[NinjaTrader_ChelseaB]

Hello Ethan,

Is this real-time or historical?

May we have output from Prints and TraceOrders() saved to a text file showing the High[1] when the order is submitted and then the order as it progresses in OnOrderUpdate()?

Below is a link to a forum post on debugging.

https://ninjatrader.com/support/forum/forum/ninjatrader-7/strategy-development-aa/99209-date-conditions-not-working?p=791121#post791121

[elcowen]

Hi Chelsea,

The Output and order seem to match up. However the bar on the chart is different from what the TraceOrders() says. So maybe its the charts wrong?

Thank you!

[NinjaTrader_ChelseaB]

Hello elcowen,

There is no evidence of any discrepancy between the bar time on the chart and the output text file.
Your screenshot does not have the databox open and is not showing the time of any bar. What are you comparing?

If you feel that the open high low and close of a bar with a specific time stamp is not matching the open, high, low, and close of a bar with the same time stamp in the output, then print the time of the bar and the open high low and close, and on the chart show the data box with the mouse over the bar showing the open high low and close.

[elcowen]

I want to reopen this thread. Attached you can see the bar (Green bar) High/Low aren't the same as whats the output window says (this bar would be the High[1] & Low[1]). Its off by 1-2 ticks

It seems to be an issue with the previous bar? Sometime my order is 2 candles behind or moves in the middle of a candle rather than waiting until the end.

At this point I'm at a loss for how to continue. Thank you for your expertise and help!

[NinjaTrader_ChelseaB]

Hello elcowen,

I am seeing the print on bar 12:08:56 with the High0] at 3861.75 and the second screenshot showing that bar's high at 3862.

However, the print shows the previous bar has a high of 3862.

Is it possible the print is incorrect and the label is with the wrong value?

Or is it possible that TickReplay was enabled and the wrong bar was referenced?

Below is a link to a video testing for this behavior. I am not able to reproduce.

https://drive.google.com/file/d/1zdX9qmi8_gPZenK-ArNX7E3cFXA0qSS_/view?usp=drivesdk

Using the attached test script and the exact steps shown in the video, are you getting different behavior?
PrintBarTime_NT8.zip