LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

remote matlab script

Craig,
 
I followed up on your communication with your local support engineer.  After looking through your VIs (that you submitted to the support engineer), it appears that you're not having trouble with interp2, but instead with either the meshgrid or griddata function.  Our engineers are currently looking into this.
 
On a different note, I noticed the VIs that you submitted took a long time to recompile.  One of your mathscript nodes contains around 450 lines of code (we recommend less than 100 per node).  Currently, compilation performance of mathscript nodes decreases exponentially as the script increases in size.  If this is a problem for you, I'd recommend splitting the script into multiple nodes or create functions out of part of the script.
Travis H.
LabVIEW R&D
National Instruments
0 Kudos
Message 11 of 13
(996 Views)

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

LabVIEW 2012
0 Kudos
Message 12 of 13
(976 Views)

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 :-).

Travis H.
LabVIEW R&D
National Instruments
0 Kudos
Message 13 of 13
(924 Views)