LabVIEW
Search Sorted Array Incorrect Output
Solved!
@altenbach wrote:
Can't do the performance testing because I don't use any VIPM tools 😄.
Okay well I included all the variations in the zip, other than the OpenG method. So you can delete the OpenG entry from the enum, and delete the OpenG frame from the case structure and the rest will run just fine.
It does do a check to make sure the outputs are all the same, and it will stop if it isn't. This has caught a few edge cases in my code already. So glad I did a little unit testing.
If the nearest has some value, even when it isn't found, then it can be returned like you said. I just didn't think of any use for it but having the length be 0 should be fine, even if you got an array subset using the output, but didn't check the found output for some reason.
