Slacter

I work with First LEGO Leagues on the side. Working with middle school students on engineering practices is excellent stress relief from regulated industries.

The recursive VI approach along with the Build Array is not memory efficient. Seems a more complicated solution. My preference is the preallocation of arrays with the swap/cut method. Focusing exclusively on timing, it appears that about 80-90% of the time expense of these routines is taken up by the Search/Split String primitive. Even changing out the swap/cut method for a build array only increases processing time by 10%, whereas deleting the Search/Split String and replacing it with a constant zero on the case input reduces overall timing 80-90%. This shows that no real significant timing gains can be achieved without a focus on improving the primitive. EDIT: Ok, just read page 2 (duh, should make sure I remember to flip the page!) I did assume that the match could be anywhere in the string.

My favorite multi-mouse utility (and the only one I've tried, thus my favorite) is MS Mouse Mischief. I wanted to have a way to make teaching my FLL teams more interactive. It's fun to use in a classroom setting. Might be nice to have for a classroom environment, but I can't quite see an application in the industrial arena. Something about having too many engineers in the code at the same time... Maybe it would make a great NIWeek competition event to see which team of 5 can program a solution in one VI the fastest...but I digress.

The sample assumes that the Data Array Col 1 values are found in the same order that they would appear in the Main Array. Try swapping your 6 and 7 position and you'll find the 0.08 and 0.03 don't populate correctly. How would you handle duplicate Data Array values in Col 1? The existing code uses only the first found and ignores the rest. Would you want to change to the last found, or do you need to keep track of all instances? In case you're up for the challenge, the intended functionality can be obtained using the following: 2 - Index Arrays 1 - Search 1D Array 1 - Replace Array Subset 1 - For Loop 1 - Case Structure FYI: The functionality using the above would use the last found occurrence and keep only that value. If data loss is not desired, then a little rethinking is in order.

Could be there for a while. I remember revisiting the Museum of Science and Industry back in the early '80s, and then again recently in the early 2000's. The same TI-99's I saw in the '80s were still in use on a couple displays.

Just recently took the CLA-R here. Preparation mostly consisted of re-reading the Advanced Architectures book I received back in 2008 and brushing up on the new stuff since, such as LVOOP. Four years ago, I don't recall a separate project management course, so I do think I could have benefitted from one now. I do feel that some of the answers on project methodology could be judged as personal preference or related to how one's own company would want to do business. However, I did pass after my first attempt. Two more years!

I've learned something new today.

Yup. Vision has a separate license that must be purchased from National Instruments...then a key shall magically appear in your inbox. This started way back with...what, LV6?

Have you tried using the VI Properties >> Window Appearance >> Custom "Show front panel when called" and "Close afterwards if originally closed" checkboxes on your top level VI? If this isn't desirable, how about trying the FP.Close invoke node upon exiting? I personally would avoid the Quit LabVIEW VI. I don't find it to be a gracious way to shut down an application. Letting the top-level VI complete its execution and closing afterwards is smoother.

Hey ev'ryone! Just thought I'd join the forum after visiting the home page a few times. Been programming LabVIEW since 1996, and extensively since 2003. I received my CLA in June 2007. I went to Michigan Technological University for Electrical Engineering, graduating in 1994. My first NI code was written in LabWindows/CVI back in 1995, but I soon migrated to LabVIEW. I programmed off and on from 1996 to 2003, where I then found a job programming in 5.0.1. I am now working hard to get my company up-to-date with LabVIEW 8.