|
PureBytes Links
Trading Reference Links
|
Rod:
MRK is one of the issues I collect and it is indeed damaged (until 1332
when it straightens out). Is the repair technique something you can
describe easily?
This really messes up my data! It's bizarre that most of a day's data
collection is bad because of one bad tick.
Allan
__________________________
At 10:43 AM 7/14/98 -0500, J. Rodney Grisham wrote:
>Mr. Bill Cruz,
>
>Remember earlier this year, during the period of January through
>March and possibly later, we had a long running discussion on
>the phone and by email discussing what Omega should do to
>correct the awful problems caused for your TradeStation 4 users
>by bad initial ticks. Igor Uhrik, another TradeStation user,
>also provided many details about the problem.
>
>In the end, you finally just said Omega could/would NOT fix the
>problem in version 4. You further promised this would not be a
>problem in version 5, which was scheduled to be released before
>today. Given the current release schedule of TS 5, I think you
>need to revisit this issue and provide a solution in version 4.
>
>On June 18 I posted the following to the omega-list discussion group:
>
>> If you are collecting stock data from BMI on LLY, you should
>> check the tick data for today. I got one of those very bad
>> initial ticks which causes such grief for Tradestation users.
>> The sooner you fix it, the fewer changes you will have to make,
>> if you remember the last time this problem was discussed on
>> this list.
>
>Today, there is a similar situation for MRK. All of your users
>are going to have to go through a painful, slow, tedious set of
>data edits to correct MRK data for today. While this problem is
>not a daily problem, it does occur; and when it occurs, it causes
>your users a lot of totally unnecessary grief.
>
>As I told you in the winter/spring, there is really no excuse for
>Omega not to automate this error correction process for your users.
>If tick corrections can be made by hand, Omega can automate the
>process. I gave you a list of several possible implementation
>strategies for a "solution." The simplest from Omega's stand point,
>and at least workable for users, is to simply make the data for one
>symbol for one day available in an external, editable file. This
>could be edited then imported if you would provide this type of a
>data management utility. As I told you in the winter and spring,
>you do not even have to change TradeStation. You could provide a
>program to read an omz file and write an editable file. Or you
>could simply define the omz format, so users could do your work
>for you. There were other options which I suggested. If you have
>lost all our written correspondence, I can send it again. I also
>have believe I still have my written notes from our phone
>conversations, which could be made legible and forwarded if your
>memory of our discussions has failed.
>
>Please revisit this request and give serious thought to providing
>a solution for TradeStation version 4 users promptly. Waiting
>for the release of version 5 was not satisfactory then, and it
>still is not satisfactory today.
>
>Rod Grisham
>
|