|
PureBytes Links
Trading Reference Links
|
Anyone tracking the bmi symbol 'indu' mic--and seeing probably a
thousand or more bad ticks in the 98/9900 range?This occured between
about 10:52-12:13 datafeed time? Just started a correct price about
12:13.
.c
Mike G wrote:
>
> Just a note to confirm I am getting the same two errors.
>
> I can't help but note that the INDU problem with the wrong opening value on the daily bar starts on Feb 29th, which might be a strange date to the software. Also, for the intraday data, the difference between the two values is suspiciously related to 65535, an important computer number.
>
> I don't know what good either of these observations does though. Still have a whole bunch of hand editing to do.
>
> Seems to me a long while ago several people were discussing how bad ticks on intraday data happened. I didn't note it carefully at the time, but there might be more clues in the archives.
>
> Mike G.
>
> >Yes, I am seeing the same thing. I am also seeing the open stuck at the
> >open for February 28th on the daily data but not the intraday data, 9854.66.
> >Each day I have to manually change it.
> >
> >BR
> >
> >From: "Gary Fritz" <fritz@xxxxxxxx>
> >
> > >
> > > I've been seeing a lot of glitches in INDU -- places where the price
> > > suddenly drops (or jumps? not sure if it's done that) by a few
> > > hundred points, stays offset for a while, then pops back up to the
> > > right price.
> > >
> > > Today I didn't see any problems in INDU. I have a 1min chart that
> > > plotted all day with no problems, and it still looks fine. But if I
> > > create a *new* 1min INDU, it's messed up. At 3:11ET it drops from
> > > 10135 to 9481, bounces between those levels until 3:15, then stays
> > > down in the 9400-9500 range until 3:49. During that time the price
> > > waveform looks right, except it's 600+pts low. At 3:49 it popped
> > > back up & down a few times, then resumed at the 10136 level, and
> > > continued properly for the final 10 minutes of the session.
> > >
> > > Since it plotted correctly in realtime, apparently I received the
> > > data correctly. But somehow it got stored wrong. So I'm guessing
> > > this is NOT a BMI problem (bad ticks etc), but some kind of problem
> > > on my end. Any idea what causes this, and how to fix/avoid it?
|