Hi Derek,
MinMax should not report a NaN as a max Value.
I couldnt' reproduce this at first, but then after some quick further testing realized that this does happen in two cases ..(1) If all the elements are NaN (which makes sense) or (2) If the first element of the input array is a NaN (which is a bug).
Is this what you see ?
MinMax works correctly for me if there are multiple(but not all) NaNs in my input array, and as long as the first element is NOT a NaN.
If this is the case, you could simply check for the 1st element being NaN and then use MinMax accordingly
Hope this helps some...
Best Regards,
Nandan
Nandan Dharwadker
Staff Software Engineer
Measurement Studio Hardware Team