www.OzSuper.com

Stock Trading => OzSuper comment => Topic started by: Ian on March 19, 2007, 07:21:37 PM

Title: OzSuper has increased its maximum time frame for charts from 1 to 2 years...
Post by: Ian on March 19, 2007, 07:21:37 PM
OzSuper has increased its maximum time frame for charts from 1 to 2 years. The timeframe has a performance impact for OzSuper web site so was originally set to a moderate 1 year. This doubling of the timeframe provides a great method of better seeing the bigger picture on a stock.

OzSuper will continue to monitor this limit, and a further expansion of time is possible in the future.

The standard options on the Company Home pages are:

30 days Price Candle Stick Charting …. http://www.ozsuper.com/ax_b2/b_CML.php?n=30#Chart
150 days Price Candle Stick Charting … http://www.ozsuper.com/ax_b2/b_CML.php?n=150#Chart
356 days Price Candle Stick Charting… http://www.ozsuper.com/ax_b2/b_CML.php?n=356#Chart
750 days Price Candle Stick Charting… http://www.ozsuper.com/ax_b2/b_CML.php?n=750#Chart
Title: OzSuper has increased its maximum time frame for charts up to 4 years...
Post by: Ian on May 03, 2007, 03:42:34 AM
What the heck, the timeframe for OzSuper Charting has now been increased all the way up to 4 years.
as follows:

http://www.ozsuper.com/ax_b/b_NAB.php#Charting (http://www.ozsuper.com/ax_b/b_NAB.php#Charting)
30 days Price Candle Stick Charting
150 days Price Candle Stick Charting
356 days Price Candle Stick Charting (1 year)
750 days Price Candle Stick Charting (2 years)
1000 days Price Candle Stick Charting (4 years)  

eg: http://www.ozsuper.com/ax_b2/b_NAB.php?n=1000#Chart (http://www.ozsuper.com/ax_b2/b_NAB.php?n=1000#Chart)
Title: 2004 Jan thru May - RANK% correction... Completed
Post by: Ian on May 06, 2007, 01:05:46 PM
The extended timeframe has exposed some bad RANK% values in the database 2004 Jan through May, Stocks were shown as having solid bad performance throughout this timeframe. Until the charts extended back into this time period, the problem had been undetected. The values have been investigated and corrected. All values have been recalculated.

The problem turned out to be a one line error in program code.

All better now.