Data flow: Difference between revisions
New page: Data flow is the fundamental tenet by which LabVIEW code is written. The basic philosophy is that the passage of data through nodes within the program determines the order of execution of ... |
No edit summary |
||
| Line 2: | Line 2: | ||
Often a single input is used as a common "thread" running through several VI's and the program to force the order of operations. Examples include the error cluster or the refnum data structure. | Often a single input is used as a common "thread" running through several VI's and the program to force the order of operations. Examples include the error cluster or the refnum data structure. | ||
== See Also == | |||
{{Portal|Getting Started}} | |||
Revision as of 08:43, 19 March 2007
Data flow is the fundamental tenet by which LabVIEW code is written. The basic philosophy is that the passage of data through nodes within the program determines the order of execution of the functions of the program. LabVIEW VI's have inputs, process data and produce outputs. By chaining together VI's that have common inputs and outputs it is possible to arrange the functions in the order by which the programmer wants the data to be manipulated.
Often a single input is used as a common "thread" running through several VI's and the program to force the order of operations. Examples include the error cluster or the refnum data structure.
