|
|
Home
Search
Register
Login
Blogs
Recent Posts
| Viewing User Profile for: aQuant | |||||||||||||||||||||||
| About | Contact | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| Post Statistics | |||||||||||||||||||||||
|
aQuant has contributed to 26 posts out of 18148 total posts
(0.14%) in 1,918 days (0.01 posts per day).
20 Most recent posts:
IQFeed Datafeed Wish List »
Level2 (Market depth) should include order count field Sep 22, 2017 09:29 PM
(Total replies: 5)
Almost 2 years later, any update on this topic? Is this still on your roadmap, any closer? Thank you.
IQFeed Datafeed Wish List »
Level2 (Market depth) should include order count field Jan 16, 2016 11:38 AM
(Total replies: 5)
Is there any update on the above? Was it internally discussed? What is the conclusion? Thank you.
IQFeed Datafeed Wish List »
Level2 (Market depth) should include order count field Oct 21, 2015 07:06 PM
(Total replies: 5)
Thank you. I did send an email. I think this feature is catering to advanced audience-but the more precious for those knowing how to use the information. It would be very valuable to have it.
IQFeed Datafeed Wish List »
Level2 (Market depth) should include order count field Oct 20, 2015 09:35 PM
(Total replies: 5)
I would like to receive order count in addition to the already available price/quantity information for Level2 data as shown here: http://www.cmegroup.com/confluence/display/EPICSANDBOX/Market+Data+-+Multiple+Depth+Book It should be very easy to implement and you are already getting the data from CME, just a matter of passing it on to users. Please let me know your thoughts. Thank you.
IQFeed Developer Support »
CME protocol May 5, 2015 01:48 PM
(Total replies: 28)
Actually, apologize to bother you. I have found the link, here it is for those interested: http://www.cmegroup.com/confluence/display/EPICSANDBOX/MDP+3.0+-+Trade+Summary
IQFeed Developer Support »
CME protocol May 5, 2015 01:11 PM
(Total replies: 28)
CME documents bundling somewhat in their documentation of MDP3, it's not detailed enough however. Could you shed light (very briefly) on how they bundle those trades in the new protocol?
IQFeed Developer Support »
CME protocol Apr 21, 2015 01:40 PM
(Total replies: 28)
Excellent, appreciate your efforts as always.
IQFeed Developer Support »
CME protocol Apr 21, 2015 01:37 PM
(Total replies: 28)
Thank you. Once you switch to that protocol, do you have plans to include microsecond precision time stamps provided by CME?
IQFeed Developer Support »
CME protocol Apr 19, 2015 09:27 PM
(Total replies: 28)
I would like to find out what protocol IQFeed uses to access cme's data, is it MDP3?
IQFeed Developer Support »
IQConnect crashed simultaneous on separate accounts in different states Jan 16, 2015 08:52 AM
(Total replies: 18)
Note that I do mention multiple clients above, but in this case I only had one client/application using the feed.
IQFeed Developer Support »
IQConnect crashed simultaneous on separate accounts in different states Jan 16, 2015 08:44 AM
(Total replies: 18)
My connection crashed today too-without any attempt to reconnect. This is the first time I experienced iqconnect.exe completely shutting down without any warning. On a positive note, I really like your data/service overall. The reconnection/handling of multiple clients has always seemed an unstable feature of this feed and has caused me to lose data on a number of days over the years I have been using it-I do save full L1 and L2 data so there is no way for me to get them from historical download once the connection is down/not reset properly. I really wish this could be made stable, it would save a lot of trouble to a lot of people who use this feed for serious analytics.
IQFeed Developer Support »
Zero bid/ask sizes for some live updates in Level1 feed. Oct 17, 2014 03:50 PM
(Total replies: 4)
Yes, I am aware of the historical data restriction. All of this is live data. Thanks, will check my data after Oct 1st.
IQFeed Developer Support »
Zero bid/ask sizes for some live updates in Level1 feed. Oct 17, 2014 03:41 PM
(Total replies: 4)
Hello, I can check in my current data, could you specify starting date from which I shouldn't see it? Also, does it require by any chance using the latest version of IQFeed, currently I am using 5.0.0.14. Finally, has this been-to your knowledge-an issue that has existed for ever/long time or was it just a temporary occurrence (if yes, what date ranges). Thank you.
IQFeed Datafeed Wish List »
Sequential Level1 and Level2 updates. Oct 17, 2014 02:50 PM
(Total replies: 0)
Hello, one thing that may be beneficial to sophisticated individuals with a limited budget (below NaNex prices) would be if Level1 updates and Level2 updates could come in a single sequence just as they do from CME for example. In other words the two feeds which are now 'independent' entities would come in a single sequence so that synchronization is guaranteed. For sophisticated orderflow analysis one needs to see certain events in the sequence they happened (trades interleaved with bid/ask size/orderbook updates). It is practically impossible to synchronize two independent L1 and L2 feeds even with millisecond timestamps-other than assuming neither of the feeds has any errors/omissions. Is an implementation of this feature conceivable?
IQFeed Developer Support »
Zero bid/ask sizes for some live updates in Level1 feed. Oct 17, 2014 02:43 PM
(Total replies: 4)
I found that these happen quite a bit (especially in certain special fast conditions). Note that the third line below ('ba' update) shows 0 ask size at 97.97 price. I was able to match this particular sequence with market depth MD01 updates and there the size shows 14. Is there an explanation for this? (this particular sequence is from August, 6th, 2014 CLU4 contract). Can provide more examples if needed. Q,QCLU14,97.96,80692,1,97.96,97.97,4,15,,10:36:14.241,5299981,10:36:14.242,10:36:14.131,b, Q,QCLU14,97.96,80693,1,97.96,97.97,4,15,183,10:36:14.276,5299992,10:36:14.242,10:36:14.131,C, Q,QCLU14,97.96,80693,1,97.96,97.97,3,0,,10:36:14.276,5299992,10:36:14.276,10:36:14.276,ba, Q,QCLU14,97.96,80693,1,97.96,97.97,3,15,,10:36:14.276,5299992,10:36:14.276,10:36:14.277,a, Q,QCLU14,97.96,80693,1,97.96,97.97,3,16,,10:36:14.276,5299992,10:36:14.276,10:36:14.277,a, Q,QCLU14,97.96,80693,1,97.96,97.97,3,17,,10:36:14.276,5299992,10:36:14.276,10:36:14.277,a,
IQFeed Developer Support »
the parameter is incorrect May 22, 2013 11:57 AM
(Total replies: 10)
Great you found the source of error. Do you have any idea when you will be releasing the new corrected version?
IQFeed Developer Support »
the parameter is incorrect May 21, 2013 04:05 PM
(Total replies: 10)
Some info on my side: applications using 4.9 protocol don't use (or subscribe) to Level2 data. Only the application running 5.0.x protocol (latest official release) uses Level2 data. Here are a few lines of raw Level2 data, at some point between 0-1am CST I was disconnected from Level2 (not sure if it was internet outage on my side). Here is how a correct time stamp message looks like before disconnect: 2~NÍ#Ð;T,20130521 01:00:15 (note: the part starting with "2~" and ending with ";" is my own stuff, rest is IQfeed generated) Here are a few lines at and after disconnect: 2,@SFM13,MD01,1.0327,1.033,8,2,01:42:27.612,2013-05-21,52,01:42:27.613,T,T,T, 2,@SFU13,MD02,1.0335,1.0341,9,8,01:42:27.613,2013-05-21,52,01:42:27.613,T,T,F, 2,@SFU13,MD03,1.0334,1.0342,9,9,01:42:27.612,2013-05-21,52,01:42:27.613,T,T,T, T 2~Ѭ?4Ó#Ð;TQY~U¤¸ëÖ‚>²gqüLu¹œ†6E›êjÙæ+ìïÓ¶'È 2~8²8Ó#Ð;S,SERVER DISCONNECTED 2~`z“;Ó#Ð;S,SERVER DISCONNECTED 2~ƒ©;Ó#Ð;S,SERVER CONNECTED O 2~k±ò;Ó#Ð;2,QMGCM13,MD01,1396.1,1397.1,2,2,01:42:28.109,2013-05-21,52,01:42:21.169,T,T,F, 2,QMGCM13,MD02,1396.,1397.8,1,1,01:42:28.109,2013-05-21,52,01:42:21.169,T,T,F, 2,QMGCM13,MD03,1395.,1398.,1,1,01:42:28.109,2013-05-21,52,01:42:21.169,T,T,F, 2,QMGCM13,MD04,1394.6,1398.4,1,1,01:42:28.109,2013-05-21,52,01:42:21.169,T,T,F, 2,QMGCM13,MD05,1394.2,1398.8,1,1,01:42:23.743,20130S,BINARY_HEADER1,COMPRESSION_TYPE1,52,01:42:21.169,T,T,T, Z,QSIN13,MD05,22.785,22.83,12,10,01:42:40.707,2013-05-21,52,01:42:41.209,T,T,T, Z,QSIN13,MD06,22.78,22.835,10,9,01:42:40.707,2013-05-21,52,01:42:41.017,T,T,T, Z,QSIN13,MD10,22.76,22.855,8,2,01:42:40.989,2013-05-21,52,01:42:33.249,T,T,T, Z,QSIN13,MD07,22.775,22.84,3,17,01:42:40.707,2013-05-21,52,01:42:41.017,T,T,T, Z,QSIN13,MD01,22.805,22.81,3,3,01:42:40.710,2013-05-21,52,01:42:40.948,T,T,T, Z,QSIN13,MD02,22.8,22.815,3,2,01:42:40.710,2013-05-21,52,01:42:24.763,T,T,T, Z,QSIN13,MD03,22.795,22.82,10,8,01:42:40.791,2013-05-21,52,01:42:36.493,T,T,T, Z,QSIN13,MD08,22.77,22.845,5,5,01:42:40.707,2013-05-21,52,01:42:40.767,T,T,T, Z,QSIN13,MD09,22.765,22.85,2,7,01:42:40.707,2013-05-21,52,01:42:40.767,T,T,T, Z,@SU13,MD04,1291.75,1294.,2,1,01:42:00.283,2013-05-21,52,01:42:24.769,T,T,T, After that disconnect, the connection was reestablished but since then the time stamp messages have been all gibberish: 2~‹H5TØ#Ð;TQùݤpô (again note: the part starting with "2~" and ending with ";" is my own stuff, rest is IQfeed generated) Also the above line containing "BINARY_HEADER1,COMPRESSION_TYPE1" is unexpected to me. The popups with that error have never gone away and I also noticed that I only have about 1/2 of the volume of Level2 data for today compared to most days (including yesterday), so the feed recovered somehow but not fully. Let me know what more specifics you would like, maybe I can dig them out. Similarly as the other poster, I use sockets in C# to get raw data in.
IQFeed Developer Support »
the parameter is incorrect May 21, 2013 03:29 PM
(Total replies: 10)
Also, to add, I have run the applications (4.9 and 5.0 version) side by side for a few weeks now without the issue.
IQFeed Developer Support »
the parameter is incorrect May 21, 2013 03:25 PM
(Total replies: 10)
I have exactly the same problem (and same scenario-running 4.9 and 5.0 versions at the same time), also happening today (coincidence?).
IQFeed Developer Support »
Millisecond precision-how precise? May 6, 2013 01:47 PM
(Total replies: 1)
I thought the answer to the following question could be informative for many traders using this feed. With the new millisecond precision starting in 5.0 version of the feed, how precise are the time stamps really? Are they very close to when the actual trades/quotes happened? Or, assuming some latency between exchange time and your 'collection' time, how precise are the time stamps with respect to each other (sequentially)? Some rough estimates on variability (in ms) would be great to have. |
|||||||||||||||||||||||