Talk:Cumulative standard deviation: Difference between revisions

From Rosetta Code
Content added Content deleted
(→‎n is always >0: it can be 0, indeed)
m (→‎n is always >0: fix to my ambiguous english, plus final bahaviourist note)
Line 1: Line 1:
== n is always >0 ==
== n is always >0 ==
But several examples check for <code>n ==0</code>. I don't think it is necessary in this task (but won't hurt). --[[User:Paddy3118|Paddy3118]] 22:06, 16 June 2009 (UTC)
But several examples check for <code>n ==0</code>. I don't think it is necessary in this task (but won't hurt). --[[User:Paddy3118|Paddy3118]] 22:06, 16 June 2009 (UTC)
: Not at all both: it won't hurt, and n is not always > 0. All the code I've done, and even the rest for what I can understand, provide a way of calculating standard deviation and mean, even if the first datum was not injected yet. A smart user won't call the method/function to get the mean if s/he's not put at least one value, but a dummy user could. In the OO cases, some methods shouldn't be public, and standard deviation could not be requested without adding a new value (very odd!), i.e. the only way to get stddev should be adding a new value... so that it would be a "know once and then forget" function/object. So to me it was "natural" to check for n>0, letting the user call mean, variance or whatever also if s/he's not added any value at all, without causing a division by zero problem. --[[User:ShinTakezou|ShinTakezou]] 23:23, 16 June 2009 (UTC)
: It won't hurt, and n is not always > 0. All the code I've done, and even the rest for what I can understand, provide a way of calculating standard deviation and mean, even if the first datum was not injected yet. A smart user won't call the method/function to get the mean if s/he's not put at least one value, but a dummy user could. In the OO cases, some methods shouldn't be public, and standard deviation could not be requested without adding a new value (very odd!), i.e. the only way to get stddev should be adding a new value... so that it would be a "know once and then forget" function/object. So to me it was "natural" to check for n>0, letting the user call mean, variance or whatever also if s/he's not added any value at all, without causing a division by zero problem. Of course for the task purpose it is not strictly necessary (real usability is not a requirement), nonetheless, it won't hurt and it assures that the behaviour is "good" for any input or misusage... --[[User:ShinTakezou|ShinTakezou]] 23:23, 16 June 2009 (UTC)

Revision as of 23:29, 16 June 2009

n is always >0

But several examples check for n ==0. I don't think it is necessary in this task (but won't hurt). --Paddy3118 22:06, 16 June 2009 (UTC)

It won't hurt, and n is not always > 0. All the code I've done, and even the rest for what I can understand, provide a way of calculating standard deviation and mean, even if the first datum was not injected yet. A smart user won't call the method/function to get the mean if s/he's not put at least one value, but a dummy user could. In the OO cases, some methods shouldn't be public, and standard deviation could not be requested without adding a new value (very odd!), i.e. the only way to get stddev should be adding a new value... so that it would be a "know once and then forget" function/object. So to me it was "natural" to check for n>0, letting the user call mean, variance or whatever also if s/he's not added any value at all, without causing a division by zero problem. Of course for the task purpose it is not strictly necessary (real usability is not a requirement), nonetheless, it won't hurt and it assures that the behaviour is "good" for any input or misusage... --ShinTakezou 23:23, 16 June 2009 (UTC)