LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview is a user-interface based software in a test analysis environment. Can we measure its robustness, user satisfaction? How?

Hello All,

 

I'm working on a code (vi) in LabVIEW to assist in analysis of data acquired from a ultrasonic probe. Now the data acquired is in the form of text files with a size ranging approximately from 10's to 100's of MB. The content stored is in the form of numbers (amplitudes) captured by the sensor when run across a piece of metal (with flaws in it; purpose of experiment being - flaw detection). To read this data and to orient the position of the flaw I have made a vi (with couple of sub vi's).

 

That was a background, my question is: If I were to use this software to just read and analyse the data, what is the required amount of automation expected to be done? Can be measure a LabVIEW code in terms of the appearances on the front panel? Can we realise and define user satisfaction?

0 Kudos
Message 1 of 4
(2,617 Views)

mechangela wrote:

Can we realise and define user satisfaction?


Yes .......Yes.....LabVIEW Rocks.....Smiley Very HappySmiley Very Happy

 

 

Ohiofudu

CLD

Certified LabVIEW Architect.
Ohiofudu Israel

Message 2 of 4
(2,604 Views)

@ohiofudu israel wrote:

@mechangela wrote:

Can we realise and define user satisfaction?


Yes .......Yes.....LabVIEW Rocks.....Smiley Very HappySmiley Very Happy

 

 

Ohiofudu

CLD


Ditto that!

 

UltraSonic.JPG

 

White-grey incident surface

Non-grey through red magnitude of the flaw plotted where it was mesured.

 

Ben

 

PS: in the event any was wondering where i have been, wait to you see the final results.

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 3 of 4
(2,581 Views)

A "problem" with Labview. Is that it is very easy for a beginner to make a mess out of thing. Labview itself has in most cases more than good enough robustness. But a poor/bad Labview programming style. Will in most cases take away the robustness. But to blame Labview as development system for this is wrong. The correct thing is to blame the programmer.

Then working with very big text files like you. It is a quite common mistake is to read the full file into the memory. And perhaps on top on this show the text file in a indicator not really needed or even worse some local or global variables. Before you know it. You have used almost all the computer memory. Render your Labview application slow as syrup. And the user satisfaction poor at the best 



Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
0 Kudos
Message 4 of 4
(2,553 Views)