|
PureBytes Links
Trading Reference Links
|
Based upon experience using SC across 3 full versions and many years of
programming experience, I've come to conclusion that Divide By Zero and/or
Overflow messages are not only used for DBZ/Overflow errors, but are used in
lieu of proper error handling of non-DBZ/Overflow errors.
I don't remembe the details but I do remember getting both overflow and divide
by zero errors on perfectly good data using Omega's own functions and studies.
I'm faced with an excellent example right now. I have a user defined function
which provides trading signals. For testing purposes, I created an indicator
which calls the function using a series of inputs as arguments. I used the
indicator for well over a week through various iterations of the function on the
same data setup and never had a problem not of my own making. When I had
completed verifying the signals, I created a system and literally copied the
function call from the indicator to the system. I added the system to the same
chart which contains the indicator expecting to see trading signals. Instead I
get a divide by zero error!
Earl
-----Original Message-----
From: Scientific Approaches <sci@xxxxxxxxxx>
To: Omega Mailing List <omega-list@xxxxxxxxxx>
Date: Thursday, March 05, 1998 9:32 PM
Subject: Re: Floating point error in SuperCharts
>The problem with overflow errors in SuperCharts that someone else was
>complaining about is more likely due to invalid historic trading data than
>to something that has happened to the SuperCharts program code. A bad price
>quote value, such as .00000001, might cause an overflow error when
>SuperCharts divides to calculate the required chart scaling.
|