JesseA

Hi Paul, You are correct that it should just work when you built a MathScript node into an application. The MathScript node just calls some subVIs in vi.lib and they are pulled in to the application the same way any other subVIs are. If the MathScript Node does not appear on the structures palette and the MathScript Window entry doesn't appear under the "Tools" menu, it usually means that you don't have the correct license for MathScript. Try opening up NI License Manager and checking your licenses for LabVIEW 8.6.1. You need to have one of the licenses with "MathScript" in its name. Jesse

Greg, It looks like interp2d_uneven is also planned as part of the effort to bring more MathScript algorithms into LabVIEW. It seems you have a similar wish list to our internal developers! Adding more parallelism to the analysis functions is an area of active research. Automatically parallelizing MathScript for loops is also tantalizing, but we'd have to figure out a way to make it configurable in case the parallel loop doesn't perform as well as the serial one. Thanks for your feedback! JesseA LabVIEW MathScript R&D

Paul, Would the MathScript contours function (legacy name contourc) meet your needs? It returns the same data that contour uses but without popping up a plot window, so it is supported in the Runtime Engine. Greg, You'll be happy to hear that we are working to bring many MathScript algorithms into the LabVIEW palettes. All of the ones you mentioned are currently on our road map. If you have any other requests, please let us know! And just a general comment about using the MathScript internal VIs on your diagrams. I can't think of any major harm in doing this, besides the risk that the API will change between versions. For example between LabVIEW 8.6 and 2009 all of the built-in function internal VIs were refactored and renamed. If you do ever use these VIs in your application, I'd recommend making a copy of the entire hierarchy to avoid being bitten by changes like this. JesseA LabVIEW MathScript R&D

You can find the 2009 (aka 9.0) versions here: NI LabVIEW Modules and Toolkits for Image and Signal Processing

Hi captainjin, According to the MathScript help, the first input to bitshift must be a scalar, vector, or matrix of positive integers, so the results when you input zero are technically undefined. But this seems like a silly limitation, so we've reported this to LabVIEW R&D as a bug (CAR# 53118). Thanks, JesseA LabVIEW R&D