I am having some significant problems with the quality of my real-time data from Kinetick.
Whenever my trades go wrong, I always go back over them the next day.
Often, I find that the price action/candlesticks that I saw at the time are different, sometimes subtly, sometimes a little more than that, in ways that may have affected my decisions. Importantly, the change in data also affects my indicators and causes me to miss signals or chase false signals in retrospect.
I do understand that real-time data is subject to some kind of upgrading after the fact, but I never thought it would be so significant as to strategically affect my trading. Especially since Kinetick is supposed to be 'the best'.
I am running a lot of indicators, some of which are calculation-intensive, so I don't know if that affects the real-time data or not, but otherwise, I am sadly beginning to wonder if the Interactive Brokers filtered data might actually be better in that, at least, what you see is what you ultimately get. Please note I am not using Cumulative Delta in my trading so that is not an issue.
Any thoughts or ideas how to improve my situation and get better real-time data would be appreciated?
Have you raised it with DTN support? What did they say?
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following user says Thank You to Big Mike for this post:
It's basically differences in the OHLC data of the candlesticks. It isn't huge, as in the chart looks completely different after I reload the data from the historical server, but more like subtle differences that add up enough to make a difference sometimes between a good and bad entry/exit.
I guess I'm basically wondering if anyone else is plagued by this issue? Or do most people using Kinetick find the OHLC data stays pretty consistent from when the bars are being built real-time to after a data reload?
Maybe your chart refresh times are too high. The default is only twice per second. That is adjustable in chart properties.
Run your workspaces with an Output window open to check for run time errors.
Make sure that any indicators that are running with COBC false are efficiently coded. Many if not most indicators perform redundant CPU intensive processing on every tick.
Examples of bad coding techniques are failure to predefine the instances of the external indicators, calling the MIN and MAX functions on every tick, and in general executing loops on every tick where the same effect can be obtained by updating one single item in a data series.
I did try and do my homework before I posted by reading all the relevant ninjatrader help info and searching the nt board. However, some of their information is confusing.
Basically, it was my initial understanding that if you had a good data vendor like Kinetick, NinjaTrader built the bars on the chart using the vendor's time-stamped data, and thus the bars shown were very accurate as it was basically the same data that you would get from the historical data server. However, there is some confusing info on the nt board as to whether that applies to time charts only, or to tick charts as well.
I believe this is what SARdynamite is referring to but I'm not %100 sure.
It's possible that for tick charts, NinjaTrader still uses the local pc clock to build the bars even if the data is time stamped, in which case the proper synchronization of the local pc clock is still very important.
In addition to the whole issue of the pc clock, there is the issue of whether resource-intensive indicators interfere/slow down the process of building the bars in real-time or whether the bar building process is completely independent of indicator calculations.
From your emphasis on this issue, Zondor, I assume you are saying resource-intensive indicators can affect/slow down the actual bar building process and throw off the timing, yes? I would've thought they would prioritize building of the bars before any calculations are done on the indicators but I'm not knowledgeable enough on the inner workings of NT to know.
Favorite Futures: Gameplay KlownbineŽ Trading of Globex
Posts: 1,276 since Jul 2009
Thanks: 1,227 given,
The only things I can be sure of about resource intensive indicators are that they cause or exacerbate chart lag during fast markets, and that this problem is much less serious now than it was with NT6.5.
Lots of indicators do calculations that serve no useful purpose, especially with COBC =false. I have been revising many of the most common indicators to address this issue.
The most accurate possible PC clock synchronization is always a good idea. I use the free Windows NTP application that can be downloaded from Meinberg. Gomi had recommended it a year or more ago.
The following 2 users say Thank You to Zondor for this post: