LabVIEW
Quick While Loop Problem
I wasn't able to open your vi as there is a video driver mismatch. If the program isn't too complex possibly posting an image of the diagram in .png or .jpg format would help as I suspect that anyone without an Nvidia video card will have the same problem.
How "huge" is the datafile. What is the size of the plot? (Number of points in x and y)
- In any case, you are hammering the CPU like crazy, recalculating the same data over and over again using 100% of the CPU. The graph only needs to be calculated only once in the while loop and then again when one of the controls changes.
- The colormap style belongs outside the loop, since it does not change.
- You are doing a complicated song and dance with complicated FOR loops that could be done with atomic operations. (For example one of your FOR loops could be replaced by a "reshape array" operation and one with "array subset", and so on.).
- Don't use "delete from array" as a substitute for "index array". Use the right tool!
- If you unconditionally add one element per iteration to an initially blank shift regsiter array in a FOR loop, you can get rid if all that (shift registers, built array, blank array constant, etc.) and autoindex at the loop boundary output tunnel instead.
- I don't quite understand the math you're doing. Isn't there an easier way to get the determinant from the 9 inputs than building and manipulating all these matrices???
Ah, that looks much better ;). You are still hammering the CPU, so you should use an event structure that calculates the stuff on the while loop only when needed.
1600x1200x8bytes (dbl) is about 16MB and most likely you have quite a few data copes of it floating around. The size of your 3D graph is nowhere large enough to display all these details unless you are planning to zoom in dramatically. Are you? It might be worth decimating the data to a reasonable amount for display.
Note that you are using the activeX 3D graphing tools. In newer LabVIEW versions, they are now replaced by the openGL versions. I don't know how they differ in performance. They do everything in SGL, so potentially there is less memory use.
One note: "Read from spreadsheet file" has a "file open" built in, so you should delete that node. If you want a customized file dialog, use the "file dialog" from the advanced file IO palette and wire the resulting path the spreadsheet file node. You can even handle the case where the dialog is cancelled. (Most likely you want to skip the rest of the code if this happens, no need for pumping hot air ;))
Maybe I have time over the weekend to do some benchmarking with the openGL stuff.
