I've found what I think is a bug in MAMath.java. The getMinMax and
getMaximum methods (and their SkipMissingData versions) use
Double.MIN_VALUE as the default to compare to values in the array,
when I think they should be using -Double.MAX_VALUE. Double.MIN_VALUE
is the smallest positive value a Java double can hold, so if the max
value is negative, you'll get incorrect results. I've been bitten by
this in my own code a few times :)
I found this in the course of using getMinValue and getMaxValue to find
the limits of a CoordinateAxis. Any suggestions for a work-around?
Thanks,
Eric