LabVIEW
Pass/Fail counter question. [Help]
Solved!
Here's a simple example if the number of tests per sample is variable.
(Still, you would think we should have more informative output, e.g. listing the failed and passed samples).
altenbach wrote:(Still, you would think we should have more informative output, e.g. listing the failed and passed samples).
OK, here's an example for that. Please verify correct operation. 😉
(Still assumes that samples with the same name are adjacent in the input. If this is not true, we could sort first by the sample column).
@tbob wrote:
Looks a little more elegant to me.
Well, I currently don't have the opeg stuff installed, so it will not work out-of-the-box on my rig. Assuming that tests for the same sample are adjacent, mine is much more efficient, because it touches each line exactly once and does things in place. No repeated array allocations for intermediary results!
(Not even considering what is happening inside the opeg tools, Jim's main diagram allocates 5 intermediary (possibly large) arrays (integer, boolean, string, etc.), often just to reduce them to a single value one step later. For large inputs, this can mean the difference between "runs fine" and "out of memory". It would be interesting to do a performance comparison as a function of input size).
This is a LabVIEW board, not an openG board, so I strongly believe we should not rely on external tools, modules, and toolkits. Besides, if we just used canned tools, we won't learn much. 😉 (Still, the openG tools are of course great! :D)
"Elegance" has many definitions. I would argue that my solution is quite elegant by some of them. 😉 If you would flatten all subVIs of Jim's code to the main diagram and see all the things it actually does to get the same job done, you'd be shocked! :o.
Personally, I prefer to keep things simple. Similarly, all I need in the kitchen is a big knife. Others might prefer a collection of specialized tools, from food processors to very specialized gadgets that only do one thing (garlic press, tomato slicer, etc.). While they make a specific process more convenient, there is associated cost, such as setup (=download and install the openg tools), cleanup and storage (=palette bloat). Just MHO. 😄
I'd NEVER use a garlic press. I PROMISE!!!
@altenbach wrote:
[...] Others might prefer a collection of specialized tools, from food processors to very specialized gadgets that only do one thing (garlic press, tomato slicer, etc.). [...]
