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)
By the way there's a mistake in the quoted post, the variation in message size doesn't come from textual representation (I forgot we were comparing FAST and SBE) but instead that in FAST, those field values are encoded in binary to take up as few bytes as possible rather than a constant size binary representation.
Can you help answer these questions from other members on NexusFi?
Tradestation Data Integrity confirmed that they will change to the new CME data protocol this August (2015), before the CME change in September, so they have to time to trouble-shoot, etc.
Tradestation will make a formal announcement sometime this Summer to confirm the upcoming data change.
According to TS, their software engineers are aware of the impact that the new data protocol will have on Tick charts.
That said, they did not confirm nor deny if they will modify the TS platform in any way to accommodate the new data stream so as to keep their Tick charts useable.
As far as prior comments on Tick vs. Volume charts.
I have found Tick charts to be much more consistent & useable on All Volume day types (low volume days, high volume days, etc.).
Volume charts do work very well on most normal & high volume days, but are horrible on Lower Volume Days (at least on the TS platform).
On Lower Volume days, you mostly have retail traders driving the market & therefore you would need to adjust your share bar setting for the charts to be useable. Tick charts are affected on these days, but much less so given it is (or was) order based (not share based).
Thanks. Wonder how this will affect the Time and Sales within Tradestation. I think T&S is grabbing all data currently from tick and it's a reconstruct. Will be interesting to see how exchange data is reported as currently it is seen. Will there be overlaps...missing.... out of orders.
I use tradestation and while developing some stuff which is based on T&S. the developers could construct the full tape from tick charts if I did not have t&s running live. However at time of development I went with live data so did not dabble with t&s reconstructs from tick charts.
There were some recent thoughts I had about further development which would look into T&S but looking at this thread thought should wait as that would be looking at t&s reconstructs from tick charts.
Well will need to check and talk to developers if the reconstructed tape will be able to distinguish details I see today with proposed data changes.
I think we may be mixing terms in this thread. For me at least the term "bundling" refers to a data provider artificially collecting (or grouping) several trades into a packet and then once a fixed time duration has transpired the packet is transmitted, with the objective being to reduce output bandwidth. Interactive Brokers is a good example of a data provider doing this practice. This is what we up until now have referred to as "filtered" data.
It is my understanding MDP 3.0 is generating a single trade report for each individual aggressor trade that executes. Using the Big Mike 50 lot example, Mike's 50 lot trade would produce a single trade report of 50 lots in size, and within that trade report would also provide details on the individual (1, 2, 5, 12, 14 .... lot) trades that filled the 50 lot order. So in my view, this is not bundling in the classic sense. If you are concerned about that 2 lot limit order in the book that was used to fill part of Mike's 50 lot initiating trade, then the trade report provides that in the details of the report.
Now if Interactive Brokers (or some other data providers) chooses to further "bundle" these aggressor trades to achieve additional resource economy, that is completely outside the MDP 3.0 protocol as I understand it at this time.
I think some initial confusion may have arisen when we saw the details of the trade report, and the term bundling started being used to refer to the trade report details (those 1, 2, 5... lot trades) used to fill the initiating aggressor trade.
"It is my understanding MDP 3.0 is generating a single trade report for each individual aggressor trade that executes" - it's this specifically that I am interested in.
I haven't seen any documentation that states that this is the case. IQFeed seem to think it's collating trades by time.
So I'm wondering which documentation lead you to your understanding.
If you have any questions about the products or services provided, please send me a Private Message or use the futures.io " Ask Me Anything" thread
Just page down to the first image, and you can see how a msg is laid out with the trades, and the orders. The referenced example is an aggressor order that matched to multiple book levels: buy 40 @ market, and that results in trades of 10, 20, and 10 at three different prices, and matches 5 different target orders. So, this example is a little beyond what has been mentioned in this thread in that even the aggressor order is split up (has to be due to different prices), but you should get the idea if you just think of the same case where the aggressor order was a single entry vs 3.
The CME wiki is a little tricky to navigate, and a lot of info is inferred or missing (it is a wiki vs a spec), but you can get a lot of info there.
If this protocol is bundling just in the sense that they're encapsulated more data in a single packet without reducing accuracy then there shouldn't be a problem. If it also allows brokers like IB to potentially pass the data through I modified then that would be even better (although historical bid/ask would probably still be a problem).