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

Re: Bad initial ticks



PureBytes Links

Trading Reference Links

Rod:

Ahh, I see. I must have not read the post correctly or understood what you
meant. I thought you meant there was simply an errant tick out of the range. I
assume you are saying then that that first tick sets some sort or defacto range
for the day or for a packet of ticks?

Please confirm if that's indeed what you mean--Because that would be...well, it
would be, as you said, a very serious flaw and very stupid for Omega not to code
a fix for that problem immediately. Oh...that would have to get in line behind
the version 5.0 resource use, as well as the year 2000 fix and the
decimals/smaller fractions of the stock market feeds fix, etc...


Best,

Tim Morge

J. Rodney Grisham wrote:
> 
> Allan Kaminsky wrote:
> >
> > 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.
> >
> 
> As I expected, and to answer Timothy Morge <tmorge@xxxxxxxxxxxxxxx>
> in this same message, it is not just any bad tick, it is the
> first tick only, and that first tick has to be very bad.  Such as
> today, when the open for MRK was 135, but the first tick came in
> from BMI at 13.
> 
> Rod