[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bad initial ticks



PureBytes Links

Trading Reference Links

Ron:

I just tried what you said, hoping it would work. It still leaves all the
remaining ticks as bad. I even tried it again, deleting the new first tick
for the day. Still NG.

I'm also running TS4B21.

Thanks for the idea anyway.

Allan
_____________________________

At 08:40 AM 7/14/98 -1000, Ron Augustine wrote:
>      
>Please tell me if I'm missing something here, but I was able to edit and
>correct the bad MRK tick without problems.  This is the second time this
>issue has come up when I was able to correct the tick in the normal way, but
>others claim to not be able to fix it without some tedious procedure.
>   
>This is what I did:  Bring up a 1 minute chart, displaying MRK for today
>only.  Right-click to the right of the first bar on the chart and select
>"Edit Price Data" -- navigate to the bad tick, select it, and press the
>"Delete" button and save the changes.
>   
>I always fix bad ticks this way and never have had a problem with it.
>Please let me know if this fix doesn't work.  I'm running ver. 4.0, build 21.
>_____________________________________
>At 01:14 PM 7/14/98 -0500, you wrote:
>>Allan Kaminsky wrote:
>> 
>>> MRK is one of the issues I collect and it is indeed damaged (until 1332
>>> when it straightens out). 
>>
>>I doubt that seriously.  Close the window showing MRK or change
>>it to another symbol.  Then display MRK again, and "amazingly"
>>the data will be bad until the moment you display it, and data
>>moving forward in time will be correct again.  The data in the
>>server's database is being stored incorrectly.  You can see that
>>by bringing up the tick editor in the server.
>>
>>> Is the repair technique something you can
>>> describe easily?
>>
>>No, look in the omega-list archives for messages from Igor Uhrik
>>IUhrik@xxxxxxx on this subject.
>>
>>> 
>>> This really messes up my data! It's bizarre that most of a day's data
>>> collection is bad because of one bad tick.
>>> 
>>
>>Yes, Bill Cruz, it is indeed bizarre, and it is correctible, easily
>>by Omega, but tediously by users.
>>
>>Rod
>>
>>
>>
>