Gary Rubin

And the gauntlet has been thrown! EDIT: I did Boggle in LabVIEW a few years back after one of our kids was born. My wife and I used to play quite a bit, but after the kid came along we were afraid to make noise shaking the letter blocks. The LabVIEW version is much quieter. I'm leery about posting it though, as I took the letter distributions right off cubes of the real game.

Yes, going from Pascal to Lisp was like learning to program all over again.

Use the Threshold Peak Detector to find all the leading edges. Reverse the array, then use the Threshold Peak Detector to find all the trailing edges. Just remember that in the reversed case, you need to subtract the peak indices from the length of the array to get the current index values.

I agree. When I started teaching myself LabVIEW as a new hire, my previous programming experience consisted of two semesters of Pascal, one of LISP, some Mathematica, and a lot of Mathcad. I can't say that my LabVIEW code was pretty or elegant (and I'd be afraid to go back and look at it now), but I was certainly able to start producing functional code pretty quickly.

Don't know why I knew. I never played them.

Not games written in LabVIEW. The LAVA 1.x had an Arcade section.

To paraphrase yourself: "Where's the rep point?"

I don't know how important OOP and XControls are to your overall project, but that statement above bothers me a little. I don't see any reason why an intelligent, motivated person couldn't be writing their own stand-alone programs after a year of LabVIEW, even if it is once or twice a week. I will concede, though, that it all depends on the nature of the programs; mine are typically short, small-scope utilities for number crunching and display. Are we still talking about the non-programmers? And by non-programmers, are we talking about science/engineering students who just haven't had a formal programming class? Or are we talking about humanities majors? What is the purpose of this? To teach them LabVIEW? To teach them to program with LabVIEW as the chosen language? To do the subject matter work, with the programming just a tool? To have them contributing to your long-term, on-going project? If it's the 1st two (and maybe the third), then I believe your LVOOP approach is teaching them to run before they've learned to walk. I would be concerned about students (especially non-programmers) losing interest somewhat if they feel like they are getting lost in the minutiae, or don't see the end product of their work.

Are you talking about the little green circle with the plus? I thought that advanced to the the next post.

ShaunR for the avatar? Or crelf for the pun?

BTW, happy birthday Cat.

Groan...

I'm now up to 3 reputation points (woo-hoo!). Is there any way to see which of my posts got the points?

Maybe you two need semaphores. Or at least some error wires to force the correct order.

ok, that would explain why my notification of your update pointed to the old one. I thought maybe it was a bug with notifications and split topics.

jcarmody, did you split this conversation to the new topic? Regardless, did you respond to the old (License Frustrations) topic, or this new one?

Including parentheses and semicolons ShaunR, I think the rest of your post was well put too. I'm looking forward to the results of the experiment of teaching non-programmers LabVIEW.

As a non-OO programmer (LV or otherwise), I think this is only true when trying to teach programmers. IMHO, if you try to teach non-programmers OOP, you're adding an extra layer of complexity that they have to learn. To me, understanding what a For loop does is much more intuitive than trying to understand classes, inheritance, etc.

It's probably preferable to becoming shepherd's pie.

That's great!!

This is all possible in LabVIEW. You will get better responses in this forum if you ask more specific questions and show what you have already tried. People here are more than happy to help, but nobody wants to feel like they're doing your coding for you.

I have no experience with Mathscript, so I can't comment there. Matlab does have an add-on Compiler (kind of like LV App Builder). I've used it to generate standalone EXEs. It can also be used to generate a shared library (.dll), but I've never tried that. I'm not sure how you would pass your data from LabVIEW to compiled Matlab. I'm sure it can be done, but not knowing your application/CONOPS, I don't know what the best way would be.

I think it really depends on your application. Last year I rewrote most of my LabVIEW analysis tools in Matlab. It would probably be safe to say that I do my data acquisition-related code in LV, and my analysis/processing code in Matlab.

This depends on your Matlab license. I have a named-user license, so I can work on any computer on which I have an account (with Matlab installed, of course) without being connected to the company network. I regularly use Matlab in the field with no network connections at all. Cat, We've been using 64-bit Matlab on a WinXP-64 system, as well as on a 64-bit Linux system. While careless coding can certainly get me to a point where I'm spending WAY too much time waiting on the system swapping virtual memory, I have never seen an "out of memory" error on the 64-bit systems. Matlab under Linux (CentOS) seems to be a bit more efficient than WinXP-64. We have a dual boot Core i7-920, and the same code running on the same data seems to be about 10% faster in Linux than WinXP. 32-bit Matlab can occasionally have problems releasing memory from execution to execution. It does have a very useful function that tells you how much memory you have available. The output looks like this: GUI creation in Matlab feels a bit primitive compared to LabVIEW, but it certainly can be done. I agree with Biometrology's comment about "exploratory" data analysis. One of the really useful features of Matlab, especially when you're doing data analysis, is the ability to put a breakpoint in the code, then create various plots from the command prompt. I also think it's easier to do complicated number crunching in Matlab (I find the text based expressions easier to read and therefore debug/modify than the wire-based ones), and I find Matlab's plotting capabilities (especially 3D) to be much better than LabVIEW's. Gary

Oh, sorry - I misunderstood your comment. I thought you were referring to the queue refnum wire.