10-17-2006 03:06 PM
10-17-2006 03:14 PM
10-18-2006 07:29 AM
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.
10-18-2006 04:48 PM
12-28-2006 08:44 PM
12-29-2006 08:59 AM - edited 12-29-2006 08:59 AM

Message Edited by smercurio_fc on 12-29-2006 08:59 AM
01-02-2007 03:51 PM
01-02-2007
03:53 PM
- last edited on
05-15-2025
04:41 PM
by
Content Cleaner
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
01-15-2007 02:31 PM

01-16-2007 05:05 AM