Support Board
Date/Time: Sat, 23 Nov 2024 19:31:23 +0000
[User Discussion] - Question for Kiwi: "On Latest IB Data Fix"
View Count: 2732
| [2013-04-24 22:04:13] |
| Frontrunner - Posts: 20 |
|
Hi, going through the threads I came across these two posts: Re: Kiwi12 LiveTrue for better Volume at Price The solution is for IB. The issue is that they have two data feeds. The original is "live" data but to avoid the slowdown issues that faced vendors who supplied every tick they only sent a tick every 200ms (now every 100ms). The problem is that if two prices happened in that snapshot then only one showed so highs and lows of the bar or day could be missed on your chart. The volume information can be quite wrong as well by 20% or 30% and not consistently one way or another. I asked them to solve it by making that information OHLC but they didn't. Instead they produced an extra feed of "true" data which is 5 second OHLCVT bars. Its good solid information and very closely matches the true exchange information of the day (no feed is 100% perfect). But each bar occurs at the end of a 5 second period so for day traders its good to have the highs and lows right but bad to wait 5 seconds. LiveTrue runs on a TD chart. It takes all the TD bars up to the current one as correct and builds an IsCustomChart using the underlying true data. It then builds the current one based on the live data and the true data as follows: - If the time of true and live data bars has the same start then O = true open, L=lowest of live or true, H=highest of live or true, and C=live. V and T from true. The prior bar is corrected to equal true data. - If the live data bar has a later start than the true then you must be in the first 5 seconds before the first 5sec true data bar arrives so it creates a new bar entirely based on the live data. It then corrects the prior bar based on the rules above for the time equal bars. That's it. All highs, lows and data are correct within 5 seconds of occurring; the bar is responsive to immediate price moves in the 0-5 second timeframe. and Re: Updated Processing of Interactive Brokers True Data OK. Heres a version of LastBar that seems to work on live HSI. Just apply it to a the new bars and the close will bounce up and down with the closing price in real time. Also the new bar will form before the first 5 second bar arrives. I compiled it on version 873 but it will probably work on 872 as well. It starts off in candlestick mode but you can change it to ohlc if you prefer. I haven't tried it in replay mode yet. As always it only works on time based charts. Edit: I tried it in replay and don't seem to have Last, LastSize information to cause the close price to reflect live pricing. What do I need to set when recording data for that to have happened? Or does it not happen in replay? Do you recommend one of these to fix the IB delay for the most accurate price and volume data? Thank You! |
| [2013-04-25 14:30:24] |
| Frontrunner - Posts: 20 |
|
I added the livbar study and at the end of each bars time (5 min bar) this message pop up appears. Was hoping you may have a solution. http://screencast.com/t/BOBdnQerS Thanks |
| [2013-08-02 02:11:22] |
| Kiwi - Posts: 375 |
|
Frontrunner, has this issue been resolved?
|
| [2013-08-13 18:46:26] |
| Frontrunner - Posts: 20 |
|
Kiwi, sorry for the delay in responding....was out of town. yes, I was able to fix the issue, with the help of a friend. I am using the LiveTrue study with a -TD chart cloned to a non-TD chart and it is working pretty well. Is this your latest and most accurate method for using IB? ....thanks for your expertise in this matter, really appreciate it! |
| [2013-08-13 21:40:56] |
| Kiwi - Posts: 375 |
|
Yes. I use livetrue to get "live updates" on true data charts (because volume profiles on td based charts are more accurate). And I use truelive to get "corrections" on live data charts for trade entry (because it seems more valid to place the order from the live chart. Also because truelive's processing is a little less complex than livetrue's. :) Unless the SC team took the approach of buffering input to the .scid file for > 5 seconds to allow the next -td bar to arrive there really isn't a better way to do this. If they did buffer it they'd have to correct the chart to the buffer+file rather than just reading the file as I think they do now. So ... added complexity to a core function! Even if they do that it doesn't change the actual output so its probably a waste of precious time. With the high quality developments and directions they have now its better that they stick with their plans. Date Time Of Last Edit: 2013-08-13 21:41:24
|
To post a message in this thread, you need to log in with your Sierra Chart account: