Adamus
Experienced member
- Messages
- 1,898
- Likes
- 97
More historical data complexities
Another reason why my progress with the mechanical trading slowed right down is that I discovered how NinjaTrader's historical data manager which collects tick, minute and daily data from Interactive Brokers, FXCM and DTC (well, I import that manually).
The ticks from Interactive Brokers arrive on my machine without a timestamp. NinjaTrader timestamps it with the current computer time and saves it to the database.
The ticks from FXCM arrive ready-timestamped with the time on the FXCM data server, i.e. the current New York time. NinjaTrader just changes the time on the tick to the timezone on my computer - i.e. London time.
That's all well and great but on my computer something is going wrong. During March due to the onset of Daylight Saving Time in both the US and UK but at different times, I realised that NinjaTrader wasn't applying the DST to the time change it applied to the FXCM data - for reasons unknown, NinjaTrader continued to adjust the NY timestamp by -5 hours regardless of the fact that it was being transmitted an hour earlier.
So that screwed up the FXCM data by an hour from March 13th. Maybe I could have lived with that, if everything had gone back to normal on March 28th when Daylight Saving kicked in in the UK. It would have been 2 weeks worth of data out by an hour - tolerable. But in a bizarre mangling of its timezone calculations, NinjaTrader decided that NY is now running 6 hours behind us and so the data continues to be out by an hour.
I posted a few charts of the FXCM data vs the IB data on the NinjaTrader forum to get their attention, and one of their support staff had a long close look at it, but was unable to get the same problem to occur on his computer and that was that. I have to re-import all my data. And of course the tick data from FXCM is gone from their servers after 30 days so if I want to save it, I have to export it and adjust it all manually and then re-import it.
This is the NinjaTrader support forum thread.
Hopefully NinjaTrader running on my new machine will be able to handle the DST transition properly. I think I don't have time to export, adjust and re-import the tick data so I can kiss it goodbye. I guess I'll archive it - I have it from June 2010 - what a shame, almost a year's worth for the 21 highest volume currency crosses.
I haven't even looked at the DTC data to see how NinjaTrader handled the manual import. Let's just hope it was OK since it would have been done all in one day every quarter, rather than each weekend.
It took me ages staring at the chart and writing down the times in NY, London and GMT during the days of March to work out which ticks should have what timestamp. Considering my academic qualifications in school maths were all graded A, I find it insane that I have such issues with what is simple arithmetic - should I subtract 1 or not. It seems someone at NinjaTrader has got the same issue.
Rant over.
Another reason why my progress with the mechanical trading slowed right down is that I discovered how NinjaTrader's historical data manager which collects tick, minute and daily data from Interactive Brokers, FXCM and DTC (well, I import that manually).
The ticks from Interactive Brokers arrive on my machine without a timestamp. NinjaTrader timestamps it with the current computer time and saves it to the database.
The ticks from FXCM arrive ready-timestamped with the time on the FXCM data server, i.e. the current New York time. NinjaTrader just changes the time on the tick to the timezone on my computer - i.e. London time.
That's all well and great but on my computer something is going wrong. During March due to the onset of Daylight Saving Time in both the US and UK but at different times, I realised that NinjaTrader wasn't applying the DST to the time change it applied to the FXCM data - for reasons unknown, NinjaTrader continued to adjust the NY timestamp by -5 hours regardless of the fact that it was being transmitted an hour earlier.
So that screwed up the FXCM data by an hour from March 13th. Maybe I could have lived with that, if everything had gone back to normal on March 28th when Daylight Saving kicked in in the UK. It would have been 2 weeks worth of data out by an hour - tolerable. But in a bizarre mangling of its timezone calculations, NinjaTrader decided that NY is now running 6 hours behind us and so the data continues to be out by an hour.
I posted a few charts of the FXCM data vs the IB data on the NinjaTrader forum to get their attention, and one of their support staff had a long close look at it, but was unable to get the same problem to occur on his computer and that was that. I have to re-import all my data. And of course the tick data from FXCM is gone from their servers after 30 days so if I want to save it, I have to export it and adjust it all manually and then re-import it.
This is the NinjaTrader support forum thread.
Hopefully NinjaTrader running on my new machine will be able to handle the DST transition properly. I think I don't have time to export, adjust and re-import the tick data so I can kiss it goodbye. I guess I'll archive it - I have it from June 2010 - what a shame, almost a year's worth for the 21 highest volume currency crosses.
I haven't even looked at the DTC data to see how NinjaTrader handled the manual import. Let's just hope it was OK since it would have been done all in one day every quarter, rather than each weekend.
It took me ages staring at the chart and writing down the times in NY, London and GMT during the days of March to work out which ticks should have what timestamp. Considering my academic qualifications in school maths were all graded A, I find it insane that I have such issues with what is simple arithmetic - should I subtract 1 or not. It seems someone at NinjaTrader has got the same issue.
Rant over.