search

openskope / skope-interface

The new SKOPE web portal interface.
https://www.openskope.org
4 stars 2 forks source link

On graph view page change "bound" to "range +" or "range -". #161

Open jterstriep opened 6 years ago

jterstriep commented 6 years ago

For chart data, call this just Upper and Lower or Upper Uncertainty and Lower Uncertainty. “Bound” says to me this is the highest or lowest value it could possibly be, which is not the case.

Appropriate labels could be returned as part of the timeseries response.

Zodiase commented 6 years ago

Does it really make sense to say a value 1300 has an "upper uncertainty" of 1400?

abrin commented 6 years ago

change to "range"

Zodiase commented 6 years ago

image

tmcphillips commented 6 years ago

We may want to revisit this issue to clarify (to users) exactly what we mean by an uncertainty range, and how we can refer most clearly to the upper and lower limits of the range. For example, if what we are talking about is a confidence interval, then 'upper bound' and 'lower bound' are not unusual terms for referring to the upper and lower limits of the interval.

As one example of the use of the terms 'upper bound' and 'lower bound' in a simple web-based application see this calculator: Confidence interval for a mean.

tmcphillips commented 6 years ago

I'm reopening this issue. The alpha 2 release uses the terms 'upper bound' and 'lower bound' on the time-series plot when the 'Show uncertainty' option is enabled.

If these are confidence intervals, then the terms 'upper bound' and 'lower bound' are correct, but we should consider renaming the option to 'Show confidence interval' for consistency.

However, because it sounds like we don't actually have confidence intervals, we need to discuss further what we mean by 'uncertainty' and decide what to call the ends of the ranges displayed around the values in the plots.

Zodiase commented 6 years ago

we need to discuss further what we mean by 'uncertainty' and decide what to call the ends of the ranges displayed around the values in the plots.

@tmcphillips I'd suggest opening an new issue for this since this issue (at least as the title suggests) was about a simple UI tweak, for that moment.

I regret not recalling this change when I was implementing the graph with Plotly. Their demo I referenced by was using Upper Bound and I didn't notice the issue (and apparently so did the people who have checked out the CodePen demo and said nothing).

Zodiase commented 6 years ago

Feature is deployed in v0.1.27.