Setting match bounds on getClassStdDeviation might create wrong intervals #58
Description
When setting the bounds on the std deviation classes, sometimes it gets the wrong intervals as it doesn't check if the minimum value or maximum is already inside the range of the intervals set.
For instance, if the stddev is 10 and the mean is 5, but the minimum value on the data is 1, the intervals returned might be
[1, -5, 5, 15, maxValue]
When match bounds is set, after setting the stddev interval bounds, the code should check if min and max values are inside the interval and shift it accordingly. Regarding the last example, the stddev should be shifted from -1 stddev, 0 stddev, 1 stddev to 0, 1 ,2 so the minimum value is actually the minimum bound of the interval. This might create a problem when min and max value are inside the intervals, which can either be solved by ignoring the match bounds or by reducing the stddev step from 1 to 0.5 or 0.25.