1min Kinetick Historical Data

[facuevasm]

Hello guys,

Now is 09:42 EST on October 11, 2024. I just download data from the continuous contract, MNQ ##-## that Kinetick has, but the last historical candle is showing a different timestamp.... 13:42... can someone explain why? Thank you!

[NinjaTrader_ChelseaB]

Hello facuevasm,

I see you have posted in the NinjaScript Strategy Development section of the forums.

To confirm, this is a value you are printing from a NinjaScript Strategy and this is not matching the chart?

[facuevasm]

I exported historical 1min data with Ninja. This is a print of the TXT file.

Thank you!

[NinjaTrader_ChelseaB]

Hello facuevasm,

I've moved your post to Desktop > Platform Technical Support section of the forums as this is not related to NinjaScript development (programming in C#).

Are you connected to Kinetick while exporting historical data? (New historical data may have been downloaded)

[facuevasm]

Yes. Connected. What I did was download the historical data first, then export data to the TXT file.

I will be alert for your comments.,

Thank you!

[NinjaTrader_ChelseaB]

Hello facuevasm,

As the market is currently open, there is going to be new data for the current day until the market closes.

If you want to ensure there is no new data downloaded, disconnect from the Kinetick connection and only the data cached will be exported (shown in the Tools > Historical data window).

[facuevasm]

Hello Chelsea,

that's not the issue. I disconnect from Kinetick, and downloaded today data, and the last timestamp is at 14:24. Maybe Kinetick original data its on a different time zone? And then Ninja converts this data to EST?



Thank you!

[facuevasm]

I got Kinetick support response:

"Hello Felipe,

When exporting the data will use UTC as the time zone as opposed to the time zone selected within your local version of NinjaTrader.

NinjaTrader exports data in UTC by default to ensure consistency when data is shared or analyzed across different regions. This avoids complications that arise from time zone differences, such as daylight savings changes, and guarantees a uniform reference point for data regardless of where it's used."