Helmut wrote: >>> r.statistics2 is intended to be a partial replacement for r.statistics, >>> with support for floating-point cover maps at the expense of not support >>> quantiles. [1] >>> >>> r.statistics3 is intended to be a partial replacement for r.statistics, >>> with support for floating-point cover maps. It provides quantile >>> calculations, which are absent from r.statistics2. [2]
Glynn wrote: >> r.statistics2 and r.statistics3 are intended to replace r.statistics. >> But those two modules have almost nothing in common. r.statistics2 >> calculates statistics which are based upon accumulators (i.e. count, >> sum of x^n, sum of (x-mean)^n), while r.statistics3 calculates >> quantiles. >> >> If you want a work-alike replacement for r.statistics, it would be >> simpler to create a script which just runs r.statistics2 and/or >> r.statistics3 to do the work. >> >> In the event that you want both types of statistics, there could be >> some efficiency gains to be had by merging the two, but only at the >> cost of creating a module which is noticeably more complex than the >> sum of its parts. > Madi: > Thank you for the explanation! I perfectly agree that it's better to > keep a couple of modules instead of a very complex one. But from the > user's POV their names at the moment are not very informative. If you > consider also r.stats... how could the user guess what's the purpose of > them all at the first glance? Perhaps names like r.stats.*, where * is > the particular function that they perform, would be a bit easier to > understand (?) perhaps -> r.stats.cover and r.stats.quantile? we should also add r.stats (and perhaps r.univar) into this discussion. r.stats -> r.stats.summary ? Hamish _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
