|
PureBytes Links
Trading Reference Links
|
Hello Gary,
purely a guess--sort of like checking to see if your "broken" VCR is
plugged in--check to be sure you're using the same expiration month.
--
Best regards,
Jim Johnson mailto:jejohn@xxxxxxxxxxxxxxxx
Monday, March 11, 2002, 1:26:54 PM, you wrote:
GF> Has anybody seen behavior like this before?
GF> My partner and I are running the same systems on parallel TS4's.
GF> Both are running Quote.com data. We sometimes get minor data
GF> differences but no big deal.
GF> Recently, including twice this morning, his TS4 has acted weird. In
GF> one case it failed to register a signal I got. When he re-applied
GF> the same system to the same chart with the same parameters, it got
GF> the signal correctly.
GF> In another case he got a signal when I did but the price was wrong.
GF> The system computed a sell price by subtracting a value (8.0) from
GF> the Low of the current bar. The Low of the bar on his TS4 AND mine
GF> was 1532.1. His TS4 signalled a sell price of 1525.7!? 1525.7 + 8.0
GF> = 1533.7, and he didn't have ANY bars that had a Low of 1533.7.
GF> Knowing the code, I can't see any way it could have computed that
GF> value, though I wasn't at his TS so it's possible I missed something.
GF> But then he re-applied the same system on the same chart, and it
GF> calculated the correct stop price of 1532.1-8.0 = 1524.1.
GF> This is NOT a case of "bouncing ticks" changing signals between
GF> realtime and historic charts, or anything like that. These systems
GF> behaved patently wrong in realtime, and we could see it. We checked
GF> all the parameters and verified they were set up right. Then they
GF> worked right when we re-applied them.
GF> Any guesses???
GF> Thanks,
GF> Gary
|