Why ExitLong goes far from the current bar?

[ypaez]

I'm using ExitLong on a bar with
Low: 5:90
High: 5.94

But my position close at 5.84, why?
Please see the attached image

PD
I'm testing on Market Replay, my strategy is OnEachTick on time frame of 5s

[NinjaTrader_Jesse]

Hello,

Thank you for the post.

I wanted to check, does this occur in the same place each time you test the script or was this a one-time occurrence?

If this is occurring, have you at this point tried to re-download this day of data (if possible)?

Also, this could possibly come from an unsynced PC clock, could you additionally ensure that your PC clock is in sync and then retest?

1. Shutdown NinjaTrader
2. Right-click the clock in the lower right corner of your desktop
3. Select Adjust date/time
4. For Windows 10 click 'Additional date, time, & regional settings' -> then click 'Set the time and date'
5. Select the 'Internet Time' tab at the top
6. Set the server to time.nist.gov and then click Update.

If the message that appears says successful your PC clock should now be updated.
If not, select a different server from the Server: drop-down and try again (repeat until one of the servers is successful)
After updating the PC clock, please restart NinjaTrader, then right-click the chart and retest. I would also suggest re-downloading the data if possible when doing this.

I look forward to being of further assistance.

[ypaez]

Hello Jesse,

Thank you very much for your replay.

In my case I'm joined to a domain and I guess that in this case I don't have the option to sync to the internet time. But my server domain it is. I check my workstation watch & gave
me a difference of 0.007 Sec with Time.is (See the attached image)

Maybe the problem could be a bad tick. I'm going to do more tests. If I see this problem recurrent I replay the evidence again.

Regards

Yuri Paez

[NinjaTrader_Jesse]

Hello,

Thank you for confirming the time is synced.

Yes, Please let me know after further testing if this occurs again or if you are able to reproduce this again. That would at least allow for testing to see why.

Otherwise, if this does not occur again, this could potentially be an isolated event or as noted possibly data related. If possible please re-download the market replay data if you are able to reproduce this again on the current dataset to check if this is related to the replay file.


I look forward to being of further assistance.