[GRASS-dev] G7: parameter standardization: n/count, min/minimum etc

[Vaclav Petras]

We should also decide between `mean` and `average`. I vote for `mean`.

Here are some resources:
http://en.wikipedia.org/wiki/Mean
http://en.wikipedia.org/wiki/Average
http://stats.stackexchange.com/questions/14089/what-is-the-difference-between-mean-value-and-average


On Wed, Oct 9, 2013 at 8:10 AM, Glynn Clements <glynn at gclements.plus.com>wrote:

>
> Markus Neteler wrote:
>
> > we have the confusing situation of naming the same statistic in
> different ways:
> >
> > r.series | r.statistics2 | t.rast.aggregate.* | t.vect.what.strds
> > ...
> >     method   Aggregate operation
> >              options:
> average,count,median,mode,minimum,min_raster,maximum,
> >
> max_raster,stddev,range,sum,variance,diversity,slope,
> >
> offset,detcoeff,tvalue,quart1,quart3,perc90,quantile,
> >                       skewness,kurtosis
> >
> > r.in.lidar | r.in.xyz | r3.in.xyz | r.statistics
> >      method   Statistic to use for raster values
> >                options:
> n,min,max,range,sum,mean,stddev,variance,coeff_var,
> >                         median,percentile,skewness,trimmean
> >                default: mean
> >
> > I would suggest to streamline this (and personally opt for the
> > r.series way of naming the methods; e.g., the "n" is easily
> > overlooked, the "count" less so).
> > Also the order might be revisited and standardized...?
>
> I suggest standardising on unabbreviated names. I'll look into using
> the option-matching code for option values as well as names.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20131009/c10feeb5/attachment.html>