Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Thought I had saw someone asking a question about tick charts forming differently on different data feeds, but I wondered if it was just the data feed causing the difference. So while I was bored today I compared ninja vs sierra on how tick charts form with the same Rithmic data feed (well not the same, one is my normal live feed with sierra and one is a ninja sim). I noticed the bars will not look the same, mostly due to the faster update time of sierra charts, does this make theirs more accurate? I don't know, maybe @josh will have more input on that. Here are to screen shots one of ninja and one of sierra, I used an 800 tick chart of oil since that has become very popular here from @VinceVirgil's great journal. The ninja chart is on top, and will be an hour behind since it is set to cst while my sierra is set to est.
You need to make certain that the Session Times are the same between these 2 charts and you also need to make sure the counting of the ticks is from the same exact starting time between the charts.
Yes I knew about the session time difference but did not think about the starting time of the 2 charts. Will have to check my settings for the tick by tick when I get home.
Still wondering if Sierra being a faster platform than Ninja would cause a difference in the tick charts, or even volume charts for that matter.
I can not imagine that it would. Following SC's advice above, I would:
1) ensure that the session times are identical. Preferably, load one day in each chart to keep it simple.
2) make sure "new bar at session start" is enabled in SC's chart settings
3) Use SC's "Chart Calculator" tool to measure the number of bars (it's in the settings) from the first to last, and use a similar tool in NT if it exists, or count the bars manually. This will ensure that the chart scaling, which may be different between the two, does not give the appearance of them being different when in fact they might be the same.
4) Make sure that you actually captured the Rithmic data in both platforms, and did not download historical data. In NT this historical data comes from only Zen-Fire if I recall, and the historical data from SC might be different.
5) If the data is live and after all this still does not match, it is possible that some live ticks are not coming through. Best to use a service like IQFeed where you can ensure an identical backfill, and compare that way.
Either way, short of NT dropping ticks real time, or the data feed itself not transferring some ticks real time (which I have seen before on some feeds), I do not think it's possible that the update speed would make any difference, because that has to do with updating charts, not capturing data, as far as I know.
Hi Josh, does it mean an automated system on Sierra Chart can't trade on real-time feeds and update data tick by tick but with 40ms interval instead?
Or it only affects traders who watch the charts and trade with their own eyes?
That's important to me...if this is true that means I can't arbitrage
We are adding a new flag to the Sierra Chart advanced custom study and trading system interface (ACSIL), to cause the study function to be called immediately on every trade and order update. This will allow the trading system to react to new market data and order updates.
The should be used with caution though because it will increase CPU load.