Skip to main content
20-Turquoise
Jan 8, 2017 8:12 AM UTC
Solved

max( ) works and min( ) doesn't ?

  Hello, Everyone.

  From :

(1).PNG

  So the question is : Is there a reason for : " max(  ) works and min(  ) doesn't " ?

       Thanks in advance for your time and help.

              Best Regards.

Werner_E
Werner_EAnswer
25-Diamond I
Jan 8, 2017 11:49 AM UTC

Ah, I did not realize that it depends on the first item in the vector.

Anyway, that behaviour sure is not as it should be and we may call it a bug.

But I am not sure how I would like min or max to behave. Normally in Mathcad, whenever a calculation encounters a NaN, it returns NaN as result. So for consistency min and max should return NaN in the examples above. On the other hand I guess it would not do any harm and would be convenient if those functions would simply ignore the NaN's - just like my filterNaN workaround.

Based on your information we can provide another workaround by simply putting + or - infinity at the front. But both workarounds will only work for vectors and must be modified slightly differently for row and column vectors.

8 replies

Werner_E
25-Diamond I
Jan 8, 2017 9:31 AM UTC

Both, max and min, work OK the same way. NaN simply is interpreted as zero.

You may use filterNaN to get what you expect:

Translate
19-Tanzanite
Jan 8, 2017 9:33 AM UTC

min works as expected as long as the first item in the vector is not NaN.  Also works ok if the first item is NaN and the minimum is less than zero.

max has the same problem if all the terms, other than NaN, are negative.

Alan

Translate
Werner_E
Werner_E25-Diamond IAnswer
25-Diamond I
Jan 8, 2017 11:49 AM UTC

Ah, I did not realize that it depends on the first item in the vector.

Anyway, that behaviour sure is not as it should be and we may call it a bug.

But I am not sure how I would like min or max to behave. Normally in Mathcad, whenever a calculation encounters a NaN, it returns NaN as result. So for consistency min and max should return NaN in the examples above. On the other hand I guess it would not do any harm and would be convenient if those functions would simply ignore the NaN's - just like my filterNaN workaround.

Based on your information we can provide another workaround by simply putting + or - infinity at the front. But both workarounds will only work for vectors and must be modified slightly differently for row and column vectors.

Translate
Werner_E
25-Diamond I
Jan 8, 2017 3:17 PM UTC

Based on Alans observation concerning the first item in a vector here are some Min/Max replacement with one and two arguments which ignore NaN's and also can be used vectorized.

Translate
23-Emerald V
Jan 9, 2017 11:54 AM UTC

For what it's worth: Mathcad 11.

The error message for stdev is: "Encountered a floating point error.".

Luc

Translate
Werner_E
25-Diamond I
Jan 9, 2017 12:59 PM UTC

Thanks - so it was still not as consequent as we would  like it to be, but at least the outcome did not depend on the first item of the vector.

BTW, in Mathcad 15 stdev returns NaN, which I consider a better way to deal with the NaN in the vector.

Translate