Different values when in highlight execution mode.

[cjs]

I am running a vi which does a bunch of math on scalars and floating point images. When I run the vi, the output images are filled with "Not a Number" but when I go throught the vi in highlight execution mode the numbers come out as what they should be. This doesn't have anything to do with the camera not responding fast enough to supply the data for the image when in normal execution mode. I'm just testing the vi by defining an image filled with a particular value so that I can see if it is doing the math correctly. If the "NaN" result was all I had to go on (when running the vi normally) I would keep looking in my code for errors, but I get the correct numbers when I run it with execution highlighting.

Can anyon
e explain why this would be happening?

Thank you.

[aderogba]

Use Probe and Not A Number/Path/Refnum? function to capture conditions generating the NaN's. I'll also suggest using the Wait function in your vi if you are not already using it.

[LunaBlue]

Hi,

I made the expirience that function in undefined order are executed in
different order if the vi is run in highlight mode or normal mode. So it
can be usefull to put some critical functions in a sequenz for the right
order.

Niko