11-16-2007 03:55 PM
11-20-2007 06:49 AM
Hi Travis,
Thanks for looking into this for me. I may split the code into smaller sections as per your suggestion as it does slow down the performance on my PXi chassis. At the moment however i have moved most of the maths / data crunching to a faster machine on the network using data socket which is working reasonably well.
Thanks again and please let me know of any updates / ways in which i can help.
Craig
12-12-2007 02:21 PM
Craig,
This was diagnosed by R&D as a problem with the griddata function returning incorrect results with the 'cubic' setting. This was reported to R&D (# 4GAED7SF) for further investigation. I also noticed that you mentioned you were running these VIs on your PXI chassis. Are you running these VIs on LV RT (Real-Time)? If so, as a heads up, I don't think MathScript is supported on RT in LabVIEW 8.5. I believe this was done because some of the MathScript functions are currently non-deterministic. That being said, I think LV RT 8.2.x (incorrectly) allowed users to run VI code with a MathScript node. It would execute fine, but it could cause the application to be non-deterministic, which is why this was blocked in LV 8.5 RT. If you're not running on an RT, then completely disregard all of this :-).