Owning Palette: Comparison Functions
Requires: Base Development System. This topic might not match its corresponding palette in LabVIEW depending on your operating system, licensed product(s), and target.
Use the Assert Type VIs and functions in conjunction with the Type Specialization structure for the following purposes:
–Customizing sections of code in a malleable VI (.vim) for specific data types
–Forcing a malleable VI to accept only data types that meet certain requirements
–Forcing a malleable VI to decline specific data types
| Palette Object | Description |
|---|---|
| Assert Array Dimension Count | Breaks the calling VI unless value in is an array with the same number of dimensions as array type.
To check if each dimension has the same size, use the Assert Array Dimension Sizes VI. |
| Assert Array Dimension Sizes | Breaks the calling VI unless value in is an array with the same number of dimensions as array type and each dimension in value in has the same size requirement (fixed, bounded, or variable-sized) and size (for fixed and bounded) as the corresponding dimension in array type.
If you do not need to compare the size of each dimension, use the Assert Array Dimension Count VI. |
| Assert Complex Numeric Type | Breaks the calling VI unless the input data is a complex numeric type. |
| Assert Error Cluster Type | Breaks the calling VI unless the input data is an error cluster. |
| Assert Fixed-Point Numeric Type | Breaks the calling VI unless the input data is a fixed-point numeric type. |
| Assert Floating-Point Numeric Type | Breaks the calling VI unless the input data is a floating-point or complex floating-point numeric type. |
| Assert Fractional Numeric Type | Breaks the calling VI unless the input data is a floating-point, complex floating-point, or fixed-point numeric type. |
| Assert Integer Type | Breaks the calling VI unless the input data is an integer numeric type. |
| Assert Real Floating-Point Numeric Type | Breaks the calling VI unless the input data is a non-complex floating-point numeric type. |
| Assert Real Numeric or Waveform Type | Breaks the calling VI unless the input data is a non-complex numeric or analog waveform type. |
| Assert Real Numeric Type | Breaks the calling VI unless the input data is a non-complex numeric type. |
| Assert Same or Descendant Type | Breaks the calling VI unless the input data is the same as or is a descendant of the input class or interface. |
| Assert Scalar Numeric or Waveform Type | Breaks the calling VI unless the input data is a scalar numeric or analog waveform type. |
| Assert Scalar Numeric Type | Breaks the calling VI unless the input data is a scalar numeric type. |
| Assert Signed Integer Type | Breaks the calling VI unless the input data is a signed integer numeric type. |
| Assert Structural Type Match | Breaks the calling VI unless the two input data types are identical, ignoring type definitions and type names. |
| Assert Structural Type Mismatch | Breaks the calling VI if type is the same data type as any of the mismatch inputs, ignoring type definitions and type names. |
| Assert Unsigned Integer Type | Breaks the calling VI unless the input data is an unsigned integer numeric type. |
| Type Specialization Structure | Has one or more subdiagrams, exactly one of which LabVIEW compiles and executes, depending on the order and the compilation result of the subdiagram. LabVIEW declines subdiagrams in order if they have syntax errors. LabVIEW accepts the first subdiagram that does not have syntax errors and ignores the remaining subdiagrams. If all subdiagrams have syntax errors, this structure accepts the last subdiagram. Syntax errors are errors within the structure, such as broken wires, not errors caused by subVIs or other dependencies.
Use this structure to customize sections of code in a malleable VI (.vim) for specific data types. You also can use this structure in conjunction with the Assert Type VIs and functions to force a malleable VI to accept only a subset of the acceptable data types or to decline specific data types. |