soulfire

One of the best features from your prior product Quotetracker was the text/email functionality on trendline alert triggers. It freed up a lot on screen watch time. Is there a plan to bring that functionality to this product?

Typically, continuous charts are adjusted to have no rollover breaks - that's what makes them continuous. I've never had an issue until recently when TDA didn't adjust a couple of times- 1st time I noticed was the Dec 22/Mar 23 rollover. The Mar 23/June 23 rollover was adjusted fine, but the problem cam back with the June 23/Sept 23 rollover. Good idea on using split adjust to make the correction manually. That fixed the issue.

TD Ameritrade has a data problem again. ES/MES futures contracts rolled over last week and normally they adjust the prior data to form a continuous chart with the new contract. They didn't do that for this round and the new data is discontinuous from past contracts data. I'm hoping this is an unintentional error on their part that they will be willing to correct if notified.

I'm surprised TDAmeritrade has not yet discovered/resolved the data discrepancy. They have the March 23 ES futures contract starting on Sunday, 12/11, but all prior days are still the Dec 22 contract, which is why there's a gap on the Sunday open. Interactive Brokers data, @ESH23, shows the data correctly with no gap.

I'm looking at the continuous contract data for futures MES and ES, using TDAmeritrade Data. I'm not sure if it's a SW or data feed issue: The chart data still has Dec 22 continuous, but today's data is showing Mar 23 contract data, causing a break in continuity. The chart has the background label as Mar 23 continuous. I tried clearing out 2 days of data, and when it reloads, the discrepancy between Dec 22 and Mar 23 data is still there but the background label identifying the chart no longer appears.

There doesn't appear to be a start date for changing one's pricing plan. If I sign up now, I'm assuming the charging will start on Nov 1st rather than cutting into this final week?

That solved the issue- thanks!

The data screens for ES have stopped receiving data from my sources (IB/ThinkorSwim). The cutoff time was at 10AM PST. It appears the systems thinks today is operating under holiday/half day hours.

What I'm seeing is for some reason, Friday saved data doesn't show the extended session and ends at 13:15PDT. The other days show the extended session and only Fridays are truncated. I've checked my past data and it appears every Friday has data stopped at 13:15PDT rather than 14:00PDT. I use IB and Ameritrade as my datafeeds for the quarterly and continuous ES/Index Futures contracts and the Friday extended session truncation shows with both data sets.

Thanks! Will the correction be in effect just going forward, or will clearing past data result in a correct refill?

I noticed for some reason the Friday 7/12 trading session for the future index funds I listed ended at 13:15PDT, and does not have the 2nd remaining session of 13:30PDT-14:00PDT. I tried clearing the data, but it refills the same way. I waited until the Sunday Globex session started to see if that would make a difference, but it hasn't.

Will the symbology for the Micro E-Mini's be as simple as adding an "m" in front of the E-mini symbol? For example, will @ESM19 be altered to @MESM19 for its Micro E-mini counterpart? Thanks!

Thanks!

I needed to hard restart my system, and when I brought MT back up - received the following error message today. Error not see on restart of MT. Logs sent.

I've observed an interesting phenomenon and wanted to share: When shutting down MT with auto backup (all including data), or just employing backup, it can take a few minuted to complete as all the data is saved to a backup file. However, there have been times when I've had to initiate a system wide shut down or restart (Win 7) while MT was running and without initiating a shutdown on MT. What happens in these cases is MT goes through the shutdown process almost instantaneously - it's as if the normal shutdown process is greatly sped up. No new backup file is created, but there is also no lost data upon restarting MT. I've noticed this every time I did a system initiated reset/shutdown with MT running - almost immediate shutdown with no lag and no data loss on restart.