-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
geomean(::AbstractInterval)
is not correct
#173
Comments
My motivation was that:
I wonder what usecases you have, where the current |
I see. Thank you for the explanation.
I think
How about this comment (https://stats.stackexchange.com/a/386476)? Similarly to
I actually don't have use cases for
Then, how about adding a new function |
That again relates to mean/geomean of random variables, not of intervals. Basically, that's how
That's definitely a non-starter. I'm sure many potential users (a large fraction, not a large absolute number :) ) would be surprised if With geomean and collections, it has a nice property that
I wouldn't call it inconsistent, but agree that it's probably best not to define it here. As this thread shows, there are at least two different meanings |
I agree that the notion proposed by @hyrodium is the more mathematically correct one. Of course, for both rather than Strictly speaking that's not encoded by just knowing the endpoints of the interval, and it's not invariant to changes of coordinates, i.e., |
From the discussion in this thread, it seems clear that there are at least two different conflicting meanings one could assign to
|
geomean(::AbstractInterval)
was introduced in #171, but the definitionsqrt(leftendpoint(d) * rightendpoint(d))
seems not correct.See Geometric mean (wikipedia) for more information.
This correct definition has the following consistency with
mean(range(...))
@aplavin
Where did you find the original definition in https://github.com/JuliaMath/IntervalSets.jl/pull/171/files#diff-29865909ee404f36758d3fb0d2d549a636b7c5cd4967d9855c245f59b3a0bb67R6?
The text was updated successfully, but these errors were encountered: