RHBailin
-Interested User-
Posts: 44
Joined: Oct 3, 2005
|
Posted: Jan 22, 2010 08:05 PM
Msg. 1 of 4
Please repair
data for security symbols
GNVC Genvec
SCMRD reverse split 1:10 Previously symbol SCMR
Don't you get notice when symbols change????????? Don't you have a data filter????????????
This is the second time I have requested these changes. I actually called it in Wednesday. I hope this doesn't take 2 weeks like it did last time.
|
DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006
|
Posted: Jan 22, 2010 10:33 PM
Msg. 2 of 4
Hello,
I just wanted to let you know that I have compiled the data to repair SCMRD with the SCMR data, as soon as I can get an approval from the market data team I will deploy these changes. Hopefully, early to mid Monday if all goes as planned.
On GNVC, the only bar I see that looks odd is for today, but a spot check with a couple vendors verified that the high for the day was 3.29 with a last trade of 2.99. If you feel those numbers are in error we can certainly contact the exchange for verification? Or is there another issue?
I will be sure to contact you on Monday to discuss as well.
Tim
|
RHBailin
-Interested User-
Posts: 44
Joined: Oct 3, 2005
|
Posted: Jan 22, 2010 11:40 PM
Msg. 3 of 4
That's great.
To review:
GNVC The problem since Wed or Thurs has been the LOW not the HIGH. Schwab has the range as 2.34 to 3.29 ProphetX has the range as 0.0235 to 3.29 You tell me if this is a problem. For some strange reason the misquoted low of 0.02 yesterday has been corrected to 2.16 Your system seems to want to only misquote the current day. The current days data is important to me albeit delayed 15 minutes.
SCMRD Note that data all data prior to 12/21 are missing and for 12/21 and 12/22 are incorrect.
|
DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006
|
Posted: Jan 25, 2010 12:10 PM
Msg. 4 of 4
Hello,
Just wanted to update you, we are currently working on converting the history of SCMR so that it can be merged correctly with SCMRD. GNVC I have been watching and the low of 2.96 appears correct. We'll need to continue to monitor on this one to determine why the decimal precision displayed incorrectly for you recently.
Tim
|