Cat

Other than a few disappointing attempts at OOP, I've so far managed to avoid that paradigm altogether (sometimes it is true that you can't teach an old cat new tricks). Imagine my surprise when I was asked to work on a new project that's going to be written in C#. Can't get much OOP-ier than that. Guess I better dust off my copy of The Object-Oriented Thought Process.

While it was a very distressing, heart-wrenching, all around awful experience for me, I wasn't quite dying.

Reinstall 7.1.1??

A few times over the past week or so when I try to access LAVA I get variations on the following msgs: Fatal error: Out of memory (allocated 1048576) (tried to allocate 491520 bytes) in /home/lavagorg/public_html/admin/sources/base/ipsRegistry.php on line 744 Fatal error: Out of memory (allocated 11010048) (tried to allocate 48115 bytes) in /home/lavagorg/public_html/ips_kernel/classDbMysqliClient.php on line 465 Just me, or a "feature" of the server upgrade?

It's not quite *that* bad. I've had a SSP for... well, probably as long as NI has offered them, and I am always years behind on upgrading. Why the SSP?? Because, especially in the early days when there were relatively few users, and actual LV competitors, I wanted to encourage NI to keep supporting LV. I personally need as absolutely stable of a development environment as possible. I am often writing code in a place where I can't get online for help if LV starts crashing for no apparent reason. I loved 7.1.1 and didn't upgrade to 8.6.1 until after 2009 came out. I am being pushed by users to start running in a 64-bit environment so I'm starting to run LV2010 experimentally, way ahead of my usual upgrade cycle. I am somewhat dismayed by the amount of time I see "LabVIEW not responding" on the screen... So I am anxiously awaiting the upcoming "stability release". Not new features, but a reliable development environment is what gets me excited. (Tho I will have to admit I love that in 2010 code pastes to where I put it, and the cluster icon is great!)

US Fed gov't shutdown. But, there's yet another Continuing Resolution, so I have a paycheck for at least another week. Otherwise I'd be traveling to Michigan looking for a LV job.

I'll miss all of you, especially hanging with the Chick Posse (that means you, too, Norm ) I agree! However, since I'm not really sure yet if I'm even going to have a paycheck starting Monday, this probably isn't a good time to bring it up with my boss....

No NIWeek for me this year. Sigh...

Yay, John!!! (of course, you're one of those people I assumed already was a CLA!)

When you start getting real desperate... if you can, put 8.6 on the old computer, recompile, and see if your app still runs. If it does the problem might be the new computer.

So I "fixed" the problem today. I replaced the XYGraph I was using to display the data with a ... (wait for it) ... XYGraph. Yup, this was one of those funny () situations with LabVIEW where if you delete non-working code, and rewrite it the exact same way, it works fine. In this case, I just right-clicked on the graph and literally replace it with the same thing. A couple key-strokes to make it the right size and set up the cursors and it works great. I noticed a few days ago that even the 32-bit app on my 32-bit system took a loong time (20s) to do that ninth plot. It would make it thru it (unlike any other variation of apps) but it definitely had to think about it for awhile. This said to me it wasn't a 64-bit or probably even a memory problem. So, after a day and a half of trying everything I could think of, the actual fix took about 5 minutes. Sigh... I still don't have a clue *why* it's hanging at that ninth plot, but at least it's not doing it anymore.

And here I thought it really was just me. It was the first time I had saved and tried to upload a vi snippet and I figured I was doing something wrong.

Lots of experience. For some reason I keep trying to use it, even tho it rarely does anything. As Ben says, the whole calling chain has to go away before it works. You're using LV 2010, right? It should be already Large Address Aware, but if you're using 8.6 take a look here. Yes, contiguous memory is the problem with large data sets, particularily when you're trying to plot them. Before I pull in a large amount of data, I read the available system memory, divide it in half, and then decimate my data to fit in that space. Yes, it's a WAG that even that will be enough memory (not to mention really frustrating to have lots of memory out there and not be able to use it), but it's been working pretty well so far.

The code almost looks deliberately wrong, which makes me wonder if it's a school assignment??? If so, while we're all glad to help people out here, we really shouldn't be doing your homework for you.

Both around 15kB. One png and one vi. "Error loading file" was all I got back. I tried both the old loader (and on the browser that can support it) the new loader.

Yeah, I looked for something more detailed but all reports had the same lack of specifics. $2,000,000 mansion surrounded by lots and lots of grass. So are you saying that hero-ness increases in proportion to the numbers of homes (just property, no lives) that were saved? (I'm trying to help you avoid the pain of practicing for the CLA )

I'm having problems uploading files to LAVA. Two different computers, two different browsers. Is it just me? (it generally is)

There are a whole bunch of comments I could make, but first of all, what is this project for?? Work? School??

I think we've gotten to the point where you need to post some code of how you've tried to implement the suggestions Roderic and I have already made, and what's working and what's not working.

So what about this? Eight firefighters injured, 2 seriously, fighting a house fire. All 5 people inside the house got out safely. My understanding is the firefighters were injured battling the blaze, not rescuing the people. Is this heroism? If my house were on fire, and all the people (which includes my cats, BTW) were safely out, I would rather the house burn down to the ground than firefighters get seriously injured trying to put the fire out. People's lives are more important than my property.

wave1, wave2, wave3 w1pt1,w2pt1,w3pt1 w1pt2,w2pt2,w3pt2 w1pt3,w2pt3,w3pt3 w1pt4,w2pt4,w3pt4 etc...

What Roderic says. And if you use *.csv, you can use "Write to Text File" function in the File I/O Palette.

Having gone straight from 8.6.1 to 2010SP1, all I can say is that I am now spending a LOT of time watching the cursor twirl endlessly and looking at "LabVIEW not responding" messages. And this is just while doing normal things, not any large data set memory intensive things. Just installing the professional development system and drivers took 3 hours. On a brand-spanking new computer.

If the requirement is not to specifically make a *.xls file, but rather just a file that Excel can read, the easiest way to do this is to make a Comma Separated Variable (*.csv) file from your data. Then you don't have to fool around with ActiveX or .Net or anything like that. So, for example, your time file would end up looking something like timeToThreshold1, timeToStop1, duration1 timeToThreshold2, timeToStop2, duration2 timeToThreshold3, timeToStop3, duration3 ...