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

Re: Bad initial ticks



PureBytes Links

Trading Reference Links

Timothy Morge wrote:
 
> 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--

That's the situation.

> 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...

It is a serious flaw, and it is made worse by active stocks, because
the more ticks, the more packets of ticks have to be edited.
The situation that brought the discussion to the forefront in 
December/January was a bad initial tick for INTC on an active day
when Intel traded over 18,000 ticks.  With approximately 60 ticks
per packet (I forget the exact number), that is about 300 ticks
that have to be corrected.  By hand, that is a big job.

Unless Omega relents, it is indeed behind version 5 release.

Rod