PureBytes Links
Trading Reference Links
|
Here is the definitive word on the Server problem which causes the
occasional huge jump or drop in the DJIA index. Note that the problem
has disappeared in TS 5.0 (confirmed by users already on a version of TS
5.0).
Carroll SlemakerReturn-Path: <Melody.Blais@xxxxxxxxxxxxxxxxx>
Received: from h1.mail.home.com ([24.0.0.50]) by ha1.rdc2.occa.home.com
(Post.Office MTA v3.5 release 217 ID# 1-1U40000L0S0V35)
with ESMTP id com for <cslemaker1@xxxxxxxxxxxxxxxxxxxxxxxx>;
Tue, 15 Sep 1998 15:26:58 -0700
Received: from mx3.home.com (mx3.home.com [24.0.0.32])
by h1.mail.home.com (8.9.0/8.9.0) with ESMTP id PAA10961
for <cslemaker1@xxxxxxxx>; Tue, 15 Sep 1998 15:26:54 -0700 (PDT)
Received: from omegaxchg.omegaresearch.com (omegaxchg.omegaresearch.com [209.149.196.11])
by mx3.home.com (8.8.5/8.8.5-AtHome) with ESMTP id PAA20893
for <cslemaker1@xxxxxxxx>; Tue, 15 Sep 1998 15:26:50 -0700 (PDT)
Received: by omegaxchg.omegaresearch.com with Internet Mail Service (5.5.2232.9)
id <S7WTY00L>; Tue, 15 Sep 1998 18:26:04 -0400
Message-ID: <5131CB844FF0D111840600805F85967949520D@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
From: Melody Blais <Melody.Blais@xxxxxxxxxxxxxxxxx>
To: "'cslemaker1@xxxxxxxx'" <cslemaker1@xxxxxxxx>
Subject: Bad Data for INDU
Date: Tue, 15 Sep 1998 18:26:04 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
charset="iso-8859-1"
Dear Mr. Slemaker,
After speaking with the engineers who wrote the server and
the charting application, I understand the reason for the price difference
between an active/open chart and the Edit Tick dialog window. When the data
is received from the feed, it is stored in a buffer prior to being written
to the hard drive and simultaneously sent to the charting application.
The prices are sent to the chart without any type of logic
checking. However, when the data that is stored in the buffer is written to
the hard drive, the current price is checked against the first tick of the
day. If the difference between the first tick of the day and the current
tick is greater than 32,767 the data is stored incorrectly. If the price
scale is 1/100 as it is with the INDU, the maximum difference is then 327
since the decimal is moved two places to the left. The problem occurs
because the check should be against the first tick of the block and not
against the first tick of the day. Therefore, in the case of the INDU, if a
price is plus or minus 327 points from the first tick, a bad block of ticks
will be stored on the hard drive. These incorrect values will only be seen,
however, when a chart is created or changed after the data has been stored.
We will try to catch this and correct the data before we
upload the refresh files to the FTP site.
This will not occur in TradeStation 5.0 as the data is
handled and stored using a completely different protocol.
I hope this provides the information you need and addresses
your concerns about this problem being carried over into TradeStation 5.0.
If you have any further questions or comments, please do not hesitate to
contact me.
Sincerely,
Melody A. Blais
Omega Research, Inc.
Customer Support Supervisor
|