Another reason for this is performance. The storageless Univariate
implementation is a compute all or nothing design. Because of this, every
time a new statistic is added to the interface, the extra computation needed
to compute the new statistic slows down the computation of the existing
statistics.
That is why I wanted to keep the stats in the lightweight, one-pass, storageless Univariate limited to the basics -- mean, variance, min, max, sum and the things that can be derived from those (std. dev, conf intervals, etc.) I personally have many uses for such a lightweight, no-storage implementation. Most of these uses are in simulation and testing, so performance and overhead is actually a big concern. Realize that if you want to compute basic stats in one pass through a set of data, you have to do the computation somewhere and if you want several statistics, you are either going to have to pass the data multiple times or compute the quantities needed for the statistics together as you pass the data, which can usually be done more efficiently than computing them individually. Farming the statistical computations out to lots of little classes makes no sense to me. I understand, however, that I am in the minority here, so I will stop complaining about this. It is time to move on.
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
