Quote from manlycure:
There's a serious geektalk parade going on here... lol
Just to let everyone that's using I/RT know, the latest version 9.2.5 that supposedly fixes the DTN/MA tick stream problem is being recalled, use 9.2.4 I'm told.
FYI.
Quote from gomifromparis:
This chart ( http://www.elitetrader.com/vb/attachment.php?s=&postid=2355542 ) got my attention !
I coded a Cumulative Delta Vol using Ninja and eSignal feed and here is what I got live :
This was nothing near foreverstudent's chart (no lower lows in the afternoon), so I played a replay, and here is what I got :
Spot on !
chuckt or AMT4SWA, could you confirm the second one is the correct one, with lower lows on CD in the afternoon ?
Have you CD guys already experienced this kind of discrepancy between live and replay with ZenFire, or any other feed ?
Thanks a lot.
Quote from chuckt101:
interesting. Ok, I just check my connection and it looks like NT/zen is running the TCP protocol so reliability is built in. It's been a while since I studied the TCP protocol but I believe the sequencing capabilities allow for data to arrive & be assembled in the order it was sent (correct me if i'm wrong). This means whether the timestamp is correct or not, your ticks will still be constructed in the same, chronological order.
Now if this is not correct, the ticks will be received regardless (unless you experience a packet drop), and merely constructed out of order on the timeframe of milliseconds to maybe seconds. Since it's all cumulative in the end, I don't believe these minor deviations should alter your view in any significant way (unless you're watching a 1 second chart).
Also note the indicator posted on NT forums was incorrect at that time. We should make sure we're comparing apples to apples. I posted a snippet of the correct logic, which I believe sbgtrading has incorporated. I have not verified it.
Thoughts?
OK EDIT: sorry i must be having a brain lapse this morning, yes having data arrive out of order would matter because you need the correct sequencing to properly grab bid/ask/sales levels.


Quote from gpzany:
correct chuckt, TCP will resequence out of order packets to correct the order, so if there is any data sequence issue, it will be at the application layer - the algorithm used by the application.
Quote from CBpasQ:
610 tick IRT/IQ chart attached for comparisons. Also ran NT with the most recent version of the cumulative delta indicator from the NT support forum and there were some major differences from the IRT/IQ version.