From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Home Community User Groups Special Interest Groups VI Analyzer Enthusiasts VI Analyzer Enthusiasts Documents Document

VI Analyzer Enthusiasts Documents

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Test - Merge Errors Style

by Proven Zealot on
‎04-18-2013 03:02 PM
- edited on ‎10-19-2023 10:25 AM by: Member migration-bot

This test detects any Build Array or Select function that has error clusters wired to all of its inputs:

 

builderr.png

 

Both of these constructs should be replaced with the Merge Errors function.

 

This test is saved in LabVIEW 2012. Follow the instructions here to install and use this test.

0 Kudos
Comments
crossrulz
Knight of NI Knight of NI
Knight of NI
on
‎04-19-2013 07:38 AM
‎04-19-2013 07:38 AM

How does the "new" merge errors function compare to the select performance-wise?  I know the older merge errors was pretty slow and using the select was a way to catch errors efficiently at the cost of possibly losing warnings.

GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Darren
Proven Zealot
Proven Zealot
on
‎04-19-2013 10:45 AM
‎04-19-2013 10:45 AM

I just did a quick benchmark of all 4 possible error combos (0 errors, 2 errors, 1 error on top input, 1 error on bottom input) in LabVIEW 2012, and in each case it looks like Merge Errors is slightly more performant than Select. And you get to keep your warnings!

0 Kudos
Contributors