|
PureBytes Links
Trading Reference Links
|
So if there is so much concern, let's zoom in on the Y2K issues
regarding TS.
The Server
internal: no problem, Gregorian date format
external: maybe problem with datafeed, if feed sends yymmdd
importing/exporting data: importing of 'yy/mm/dd' is a problem
Charting
uses the server
Easy Language
uses the server
So the problems are with datafeeds that send dates in "yy"
format, and with importing data in "yy" format.
The solution:
Roughly three functions:
One that determines if the data is in 'yy' or in 'yyyy' format.
If the data is in 'yy**" a warning should be given that "date
format is not YK2 compliant, only dates between for instance 1920 and
2020 are processed correctly, where '00' - '20' will mean 2000 -
2020.
The next function does the conversion from 'yy' to gregorian.
The third function does the conversion from 'yyyy' to gregorian.
Should be a breeze to write for Omega. So unless there are
other problems with TS internal date calculations we should not have
to worry.
Please correct me if I'm wrong,
Regards,
---------------------------
Guus Prick
Bird sings, cat awakens
http://www.iaehv.nl/users/guus/
---------------------------
*** TFS Evaluation Copy of module : MS Exchange ***
To: TradeStation users
From: Bill Cruz, Co-CEO of Omega Research
Some of our customers have been inquiring as to why Dow Jones TradeStation
5.0
was released without a concurrent new release of TradeStation for the other
data vendors which we support.
First of all, our goal at Omega Research is to provide our customers, both
individual and institutional investors, with the most advanced trading tools
in the industry and to make our tools compatible with the most popular data
vendors.
With some data vendors, Omega Research software works directly with a data
vendor's data feed (example: Signal, BMI, S&P Comstock), in which case the
Omega Research Server is used to collect and archive the data. In other
cases, Omega Research software works with a data vendor's server (example:
Dow
Jones Markets and FutureSource), in which case the Omega Research Server
Gateway is used to simply translate the data to the Omega Research data
format.
The reason we have not yet announced a new release of TradeStation for other
data feeds is because we are still working on finishing up the newest version
of the Omega Research Server. This new Server, which is a very significant
project, will offer exciting new capabilities which will greatly empower you
as a trader.
When the new Server is completed, we will be releasing new major releases of
our products for all the feeds with which we are compatible. We also, at
that
time, plan to announce support of additional data feeds that have been
requested by our customers.
We believe that you will be very pleased with the features and enhancements
that will be added to our products. As always, existing TradeStation users
are able to upgrade to a newer release at a significantly discounted price.
Thank you for your continued support.
Best regards,
Mitch Ackles
Product Management
Omega Research
Mitch.ackles@xxxxxxxxxxxxxxxxx
(800) 292-3461
www.omegaresearch.com
Date: Thu, 11 Dec 1997 14:14:56 EST
From: IUhrik <IUhrik@xxxxxxx>
To: grisham@xxxxxxxxxxx
Cc: omega-list@xxxxxxxxxx
Subject: Re: editing ticks of ORCL
Message-ID: <c04bc703.34903bc2@xxxxxxx>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
In a message dated 97-12-11 00:08:40 EST, Rod Grisham wrote:
<<
I am sure this has been discussed here before, but I cannot
find it in the messages I have kept. Would someone refresh
my memory, please?
Today ORCL passed the magic limit of the number of ticks the TS
data editor can handle without the editor causing the server to
crash and abort. Of course, I have at least one bad tick - a one
minute chart goes to zero. Is there any way to export the ticks,
edit them externally, and then import the cleaned data? I am
talking about TS4 which uses the *.omz format to "copy out" and
"paste in."
>>
I do not know of any "external" way to edit bad ticks once a symbol
crosses 33,000 ticks. They certainly can not be edited internally, in
TS, no matter you do. The bottom line is that that bad ORCL tick on
Dec 9 made the tick collection for the stock unusable and ORCL
untradable. If you use 45 days to build your intraday chart, you'll have
to wait that long collecting data before the bad tick stops affecting your
chart. While waiting, keep your fingers crossed that you won't be hit
with another bad tick, returning you to square one, etc., etc., etc.
Send your thanks to Omega.
Concerning this problem, I wrote to Bill Cruz on June 1 (a copy of the
full text was posted here on June 2):
"...You may recall my letters as well as our telephone
conversation of last year urging you to correct TradeStation's
inability to edit symbols generating more than 13,000 ticks,
that is, the symbols for high-volume stocks that by definition
are prime vehicles for stock traders. I argued then that a
single bad tick could ruin a valuable tick collection for a
particular symbol which is an indespensable tool for trading.
When that shortcoming was finally fixed in build 16, your
technical support assured me that TradeStation would be
able to handle symbols generating hundreds of thousand
ticks a day, an assurance that seems to have been too
optimistic.
Although this problem affects stocks traders only, whose
satisfaction seems to have been a traditionally low priority
for Omega (for example, unlike future traders, the former
can not archive their valuable tick data), I hope you will
have it resolved as soon as possible..."
Then, on July 15, after another occurence, I wrote to Bill Cruz
again:
"...Once again, I urge you to have this defect fixed as
soon as possible. Frankly, I do not believe that an intraday
charting program lacking the capability to edit high volume
stocks should be promoted, explicitly or implicitly, as a tool
for stock traders. If Omega is not interested in fixing the
defect, perhaps it should consider to market TS with an
appropriate disclaimer..."
Unfortunately, Omega refused to correct this fatal law, saying it will be
corrected in TS5. That is unacceptable. The incidence of days crossing
the 33,000 tick treshold is on the rise. Since May, AMAT crossed the
treshold once. ASND and ORCL did so twice each (the latter reached
almost 113,600 ticks on the 9th, and almost 61,000 on the 10th), while
INTC went over the limit 10 (!) times.
The program is dangerous now. It may cause financial losses by
rendering your data collection worthless, and by stopping you from
trading at a critical time.
Wonder what will happen if someone gets seriously hurt because of
Omega's failure to provide a functional product in a timely fashion. It
may be a disaster waiting to happen. But note, Rod, that there is very
little interest in this issue among the members of this illustrious list who
seem to be absorbed by other subject matter. So, unfortunately, it is
up to you, and me, and the remaining one or two stock traders on this
list to get Omega to fix this serious flaw without delay. Please contact
Omega and demand an action.
Igor Uhrik
-----------------------------------------------------------
D
Date: Thu, 11 Dec 1997 15:11:06 EST
From: APutt <APutt@xxxxxxx>
To: omega-list@xxxxxxxxxx
Subject: Using Easy Language Book
Message-ID: <e20b8198.34904a46@xxxxxxx>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
I have had many E-Mails regarding my newest book on Using Easy Language. I
have a Web Page with details.
I have also created links to Omega User Groups.
Please vist my page at: members.aol.com/aputt
|