|
PureBytes Links
Trading Reference Links
|
"That is a Bridge pipeline problem that occurs as the data is
broadcast". So says FS techsupport. It is most common in the
high volume contracts. Support says it will be corrected before
Jan1. It can also occur if an FS user is not using the latest FS
data buffer patch.
In a min(.vch) file, the first instance of the timestamp is the
correct value.
Delete the latter.
In a tick(.tch) file, earlier timestamps occur after a later
timestamp.
i.e. 12:15:02 followed by 12:15:00. Delete the latter.
However, FS has a tick editor that scans the data and looks
for these and asks if you want to edit the tick when it comes to a bad
one and it should be run, at the very least, before exiting FS. I run it
daily after the rth session.
I highly advise anyone using the FS ascii file conversion utility to
run this, save the data in the FS manager, and then create the ascii
file.
dbs
Gary Fritz wrote:
> > I'm trying to look at some FutureSource data.
>
> Dennis H. nailed it: duplicate records.
>
> For some reason, about every 650-660 lines the FS data contained a
> duplicate bar. E.g. there would be 2 12:55 bars on 3/5/1999 (both
> with different data), and then about 655 bars later there would be
> another one.
>
> Apparently TS scans the data, notices two lines with the same time,
> and says "hm, then it MUST be a tick file." Sure wish it would give
> ME the option to decide what it was.... it would be a whole lot less
> hassle than what I just went through!!
>
> Thanks Dennis!
> Gary
|