|
PureBytes Links
Trading Reference Links
|
In theory it is possible to correct the data. You need to get ODBC
ctree-plus driver and off you go. However the driver is quite
expensive. In any case the Omega mechanism is a mess so that it is
not trivial to restore the original value - but it should be
possible.
Bob Brickey claimed that he loved the storage mechanism so much that
he used it for his own files. He would be the ideal candidate to
provide such a recovery tool................
Gerrit
> > Some interesting observations on the 4.0 RT quote server
> >
> > This investigation was initiated to determine what if anything could be done
> > to preclude or correct tick data overflow (wrap around) which is caused by
> > the (High - Initial Tick Value) or the (Initial Tick Value - Low) exceeding
> > 32768 divided by the symbol scale factor.
> >
> > **** CORRECTION OF TICK DATA OVERFLOW
> > It appears the only way to correct tick data in which overflow has occurred
> > is to write a program which adds/subtracts multiples of 65536 to the stored
> > tick data. Someone have a program that does that?
>
> <snip, snip>
>
> I, and others, have been round and round and round with Bill Cruz
> himself about this bad initial tick issue. Parts of the discussions
> are in the archives of this discussion group.
>
> Ignoring Bill Cruz and Omega staff and supporters, if you had the
> program you asked for, how would you get the data out of the server,
> modified, and back into the server???
>
> In other words, Bill Cruz has to cooperate with our desire to fix
> his bugs. Bill Cruz has flatly refused to provide ANY mechanism
> to make this feasible. Included in his refusals are several
> proposals which would require little or no effort on Omega's part,
> e.g. "Tell us what public domain compression mechanism you use
> to create the *.omz files?"
>
> Since you included Jim Osborn in your address list, let me add that
> this type of facility is one of the reasons Jim is still using
> TS 3.5.
>
> Good luck to you with beating on OR for just a little help with
> solving this bug.
>
> Rod
>
>
|