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)
Interesting. I had a problem again last night with my data. I can't confirm it was the same behavior as last time because I slept through it. Maybe just a coincidence, but it is rare for me to have a data loss. This would suggest it is not a SC/TT problem since I am IQFeed/IB.
At 4 am EST I changed, erased some files and got it working. went back to bed cause 6E was not moving. It was around 10 30am EST I tuned SC on same problem and price is stuck at the same level 1.3864
I got an email from VF suggesting to contact with TT. I just got off the phone with TT and they are no help either. I am told there is incorrect datafeed and there is a case with Velocity about it. So I contacted 3 sides of the equation and there is no help so far.
I haven't noticed it again, but didn't trade last night or today so don't have SC open.
Let me just say that I think SC has a good product, and their support seems to do an excellent job, but that I really hate finger pointing. It's my opinion they need to take complete ownership of the issue even if it is not their fault, and help get to the bottom of it.
My only advice is to try and get SC on the phone when the problem is occurring, so they can remote into your system and see it for themselves and try to duplicate it. And hopefully when they do, they don't just say it's a TT problem and move on. If you have another platform, I suggest running it side-by-side with SC so when the problem occurs, you can demonstrate it works on the other platform fine (but not SC) if that is in fact true.
Totally agree with you. Sometimes, they get very defensive.
By the way, has any one experienced the problem described in this thread? I sometimes notice that TT data is lagging behind my other broker (both use SC) although not as serious as described in the thread. For example my other broker chart is hitting new high, TT hits new high a little later.
I think SC with Velocity is a good product as well. But I feel that I should let them (SC and Velocity) know if there is a problem so they can fix it. Unfortunately I do not have an access to another platform. I moved from Infinity to Velocity due to commissions and availability of various platforms.
Long story short, SC has been very responsive with their prompt messages and later in the day Friday 6E and 6A were running normally at the same time. I hope that this won't happen again, I sure don't want to get caught in this when I am in a trade.
We hope we are not improperly making a posting here. The data file was simply not the problem based on all of the evidence and especially the information given to us by oztrd. We have maintained that deleting it was only coincidental when it appeared to resolve the issue (referring to post #10). We continue to maintain that. Very simply if you set up a Quote Request on a Worksheet and you don't see the last trade price update, then once again the data file is not the issue. It simply couldn't be. There was no involvement with it. In the case of a Trading DOM it is simply limited to the purpose of providing a single price until the live data feed responds with the current market price.
For a technical discussion on this, once we have a nonzero value from the data feed, then the price that you see on the right side of the chart and the price you see on a Trading DOM is 100% driven by the feed and the file simply has no longer any involvement in it. Additionally, we are intimately familiar with how chart data files are structured and how they are used in Sierra Chart. The file structure is extremely simple. It contains a header and simply repeating records that contain a simple structure of floats and integers for the OHLC data. The probability of a file truly being corrupt that affects chart updating is very very minimal an almost nonexistent these days. And at best it would only affect the price bars. Not the price box on the right side. On the NTFS file system, a corruption is a very unlikely scenario. Additionally Sierra Chart has the ability to detect and correct "corruption" issues which really relate to the file size. Corruption issues really go back to the days of fat 16.
We did contact Velocity about the problem, and asked for information about what the log files show to see if market data incremental refresh messages are being started for the last trade price. They always are but that would be the only thing we could think of which would lead to a problem from our perspective being that market depth data was being received. That's all we could do. We understood that they contacted TT about it and that's all we know. We have not heard about the issue since then and we have not made any changes that would relate to it.
Also in regards to the Rithmic issue with bad data, that's a whole different kind of matter compared to this TT last trade price issue where the feed was not providing price updates. We don't really know what the reason for that bad data was that occurred shortly after our initial release of support for Rithmic. Although once we solved a threading problem involving processing of messages from the Rithmic server, that bad data went away.
If we clearly see an issue is not within Sierra Chart, then all we can do is contact the provider of the service being used, about the problem and give our technical knowledge about it and just have to see what they will do. Once we had clear information about the last trade price not being received, and we had to be certain about that so we don't improperly raise issues, then we contacted the service about it.
Note: It is also possible Mike, that what you and oztrd were experiencing were different issues. It didn't seem like it because it was the same symbol you both had trouble with and you were both on apparently the same server and had a problem at the same time.
