LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Desire VI Metrics Tool block diagram

In the folder C:\Program Files\National Instruments\LabVIEW 8.2\project is the LLB entitled prometrics.llb.  It contains the VIs that make up the VI Metrics tool.  Although it is very useful, it has a number of areas we'd really like to tailor to meet our metric requirements.  All the files in the LLB are accessible except ProMetrics Compute Metrics for Display.vi - its block diagram is password protected.  Is there anyway to get that 'source'?
0 Kudos
Message 1 of 11
(4,123 Views)
That VI is distributed by NI, so I sincerely doubt they would open up the block diagram, as it probably is not in their best business interest to do so.
0 Kudos
Message 2 of 11
(4,118 Views)

I figured as much.  In lieu of an early Christmas gift, I'll ask another question.  In my limited use of the VI Metrics tool (and in talking with NI Tech Support), it appears that you can only run VI Metrics on one file at a time.  In most cases, the tool drills down a bit and provides the metrics for the other VIs contained within.  It didn't (at least for me) display the metrics for a number of LabVIEW 8.20 class methods (VIs) I call within one particular VI - I have no idea why.  What I wanted to do was to be able to select a number of files that collectively make up a certain test and get their metrics.  This way, I can not only collect metrics, but I can build a history.  For example, drivers are typically 300 NDCI (Nodes, Diagrams, Controls, Indicators), Test Equipment control is roughly 400 NDCI, etc.  There would be more granularity than this, of course (i.e. complexity needs to be taken into account). 

Anyway, does anyone have a suggestion for developing some type of script (or VI) that can call VI Metrics.vi for each file in a directory (or from a selection), allow me to select the desired "Show Statistics For", dump this info to a spreadsheet.  What I would then like to do is run a second utiltiy that goes through the output file and removes all redundant entries.  This way I can do a total NDCI count without counting anything twice.

0 Kudos
Message 3 of 11
(4,099 Views)
mrbean,

Even without access to the ProMetrics Compute Metrics for Display.vi source you should still be able to call it as a subVI to automate the collection of metrics.

You need to pass this subVI an array of strings containing the filenames of the VIs you want to compute metrics for.  It will then output 3 arrays of strings -- a VI name column, a metrics name row, and a 2D array of values that make up the metrics table.  Remember that you can only compute metrics for VIs loaded into memory (which you can do programatically by using Open VI Reference). 

Good luck!

Simon H
Application Engineer
National Instruments

0 Kudos
Message 4 of 11
(4,076 Views)
I finally got around to this, and I'm having trouble with it.  Using VI Reference, I see a method for opening its front panel, but I don't see one to load the VI into memory.  I don't really wish to open the FP for each of these VIs.
0 Kudos
Message 5 of 11
(4,018 Views)
You shouldn't need to do that. This little bit of code worked for me:



I had to use a frame sequence since the metrics VI has no error I/O.

Message Edited by smercurio_fc on 12-29-2006 08:59 AM

Message 6 of 11
(4,004 Views)
I'm using LV8.20 and I'm not sure what the function is that is in the 2nd frame just before the build array.  Also, what is the purpose of the reference to This Application?
0 Kudos
Message 7 of 11
(3,966 Views)
 

That is a Strip Path function, it is being used to get the filename of the VI.  You need "This Application" because in LabVIEW 8.0, the concept of Application Instances was introduced.  Read the LabVIEW Help for more information.

-D

0 Kudos
Message 8 of 11
(3,962 Views)
Hello,

    Very interested in using something like this myself. I have a huge number of vis which I would like to get some metrics from. I notice that the block diagram above uses a vi that looks  sometrhing like Compute Metrics for Display.vi within LabVIEW 7.1\project\Source Code Control\_sccsbvi, however we're using LabView 7.1 and my Compute Metrics for Display.vi is subtly different to that shown in the block diagram in that it has one less input than that shown in the block diagram. Am I missing something or is there another way to automate vi metrics over a number of vis.

Thanks in advance to any body who can help me out...

Ross
0 Kudos
Message 9 of 11
(3,901 Views)
You mentioned LabVIEW 7.1\project\Source Code Control\_sccsbvi, I didn't see anything in the similar 8.2 directory - any idea if anything similar exists and where it's located?
0 Kudos
Message 10 of 11
(3,881 Views)