Data flow - Revision history

Logmanoriginal: Change links to point to execution highlighting, remove notice about single thread

2023-05-06T16:33:25Z

Change links to point to execution highlighting, remove notice about single thread

← Older revision		Revision as of 16:33, 6 May 2023
Line 15:		Line 15:

	{\|		{\|
	\| [[File:Dataflow - Nodes execute in parallel.gif\|frame\|Nodes without data dependencies execute in parallel. (Note: [[~~#Visualizing dataflow in LabVIEW\|~~Execution highlighting]] forces the code to run in a single thread which is why they appear to execute sequentially).]]		\| [[File:Dataflow - Nodes execute in parallel.gif\|frame\|Nodes without data dependencies execute in parallel. (Note: [[Execution highlighting]] forces the code to run in a single thread which is why they appear to execute sequentially).]]
	\|}		\|}

	== Visualizing dataflow in LabVIEW ==		== Visualizing dataflow in LabVIEW ==

	~~The~~ [[~~Debugging\|debugging]] option "''~~Execution ~~Highlighting''" [[File:Execution Highlighting On.png\|border\|Execution Highlighting enabled\|link=Debugging~~]] ~~will~~ visualize the flow of data while executing a [[VI]] in LabVIEW.		[[Execution highlighting]] can be used to visualize the flow of data while executing a [[VI]] in LabVIEW.

	This, however, forces the code to run in a single thread, which causes nodes to execute sequentially<ref>[https://forums.ni.com/t5/LabVIEW/Execution-Order/m-p/2655447/highlight/true#M791922 Execution Order] (National Instruments Forums)</ref>.

	== See also ==		== See also ==

Leahmedwards: Fixed broken link to Wikipedia article on Dataflow programming

2022-10-02T19:13:16Z

Fixed broken link to Wikipedia article on Dataflow programming

← Older revision		Revision as of 19:13, 2 October 2022
Line 32:		Line 32:
	== External links ==		== External links ==

	* [[Wikipedia:Dataflow ~~Dataflow~~]] (Wikipedia)		* [[Wikipedia:Dataflow programming]] (Wikipedia)
	* [http://www.ni.com/getting-started/labview-basics/dataflow Dataflow Programming Basics] (National Instruments)		* [http://www.ni.com/getting-started/labview-basics/dataflow Dataflow Programming Basics] (National Instruments)

Q at 16:24, 14 March 2021

2021-03-14T16:24:56Z

← Older revision		Revision as of 16:24, 14 March 2021
Line 39:		Line 39:

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]
	[[Category:~~Dataflow~~]]		[[Category:Programming Paradigm]]

Logmanoriginal: /* LabVIEW dataflow model */ Fix broken gif

2019-08-28T14:11:10Z

LabVIEW dataflow model: Fix broken gif

← Older revision		Revision as of 14:11, 28 August 2019
Line 15:		Line 15:

	{\|		{\|
	\| [[File:Dataflow - Nodes execute in parallel.gif\|~~thumb\|left~~\|Nodes without data dependencies execute in parallel. (Note: [[#Visualizing dataflow in LabVIEW\|Execution highlighting]] forces the code to run in a single thread which is why they appear to execute sequentially).]]		\| [[File:Dataflow - Nodes execute in parallel.gif\|frame\|Nodes without data dependencies execute in parallel. (Note: [[#Visualizing dataflow in LabVIEW\|Execution highlighting]] forces the code to run in a single thread which is why they appear to execute sequentially).]]
	\|}		\|}

Logmanoriginal: Rewrite article

2019-08-28T07:12:57Z

Rewrite article

@@ Line 1: / Line 1: @@
-Dataflow is the fundamental concept under which the LabVIEW&nbsp;execution system executes code written in G (the graphical language used in LabVIEW). 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 nodes (functions, structures, and subVIs) have inputs, process data and produce outputs. Whenever all of a node's inputs contain valid data, that node will be scheduled for execution by the LabVIEW&nbsp;execution engine. &nbsp;As soon as a processor becomes available (subject to available CPUs and the completion of previously scheduled nodes), the node will be executed. &nbsp;
+[[Wikipedia:Dataflow programming|Dataflow programming]] is a [[Wikipedia:Programming paradigm|programming paradigm]] where the execution of functions is determined by their data dependencies. This is fundamentally different from traditional programming paradigms that execute functions in sequence as they appear in the source code.
-After a node executes, values on its output wires become valid and "flow" to the next nodes with those wires connected as inputs. By chaining together nodes that have compatible inputs and outputs, the programmer controls the order in which the nodes execute. Often a single input is used as a common "thread" running through several VI's and the program to force the order of operations, whether or not each node has any need to modify the data passing through it. Examples include the error cluster or a refnum data type.
+== LabVIEW dataflow model ==
-An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.
+LabVIEW uses the graphical programming language [[G|G Dataflow]], which utilizes wires to represent data dependencies between functions (''nodes'' in LabVIEW terminology).
-== External links  ==
+A node without input wires can execute immediately, while a node with input wires must wait until the previous node has finished execution.
-*[http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)
+{|
-*[http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)
+| [[File:Dataflow - Node without input wires.gif|thumb|left|A node without input wires executes immediately.]]
-[[Category:LabVIEW_fundamentals]]
+It is also possible to execute multiple nodes in parallel, as long as they have no data dependencies between each other. However, the total number of nodes that can execute in parallel is limited by the [[LabVIEW Execution System|execution system]].

Jdunham at 23:05, 6 February 2009

2009-02-06T23:05:25Z

← Older revision		Revision as of 23:05, 6 February 2009
Line 1:		Line 1:
	Dataflow is the fundamental concept under which the LabVIEW execution system executes code written in G (the graphical language used in LabVIEW). 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 nodes (functions, structures, and subVIs) have inputs, process data and produce outputs. Whenever all of a node's inputs contain valid data, that node will be scheduled for execution by the LabVIEW execution engine.  As soon as a processor becomes available (subject to available CPUs and the completion of previously scheduled nodes), the node will be executed.		Dataflow is the fundamental concept under which the LabVIEW execution system executes code written in G (the graphical language used in LabVIEW). 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 nodes (functions, structures, and subVIs) have inputs, process data and produce outputs. Whenever all of a node's inputs contain valid data, that node will be scheduled for execution by the LabVIEW execution engine.  As soon as a processor becomes available (subject to available CPUs and the completion of previously scheduled nodes), the node will be executed.

	By chaining together nodes 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 a refnum data type.		After a node executes, values on its output wires become valid and "flow" to the next nodes with those wires connected as inputs. By chaining together nodes that have compatible inputs and outputs, the programmer controls the order in which the nodes execute. Often a single input is used as a common "thread" running through several VI's and the program to force the order of operations, whether or not each node has any need to modify the data passing through it. Examples include the error cluster or a refnum data type.

	An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.		An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.

Jdunham at 22:58, 6 February 2009

2009-02-06T22:58:55Z

← Older revision		Revision as of 22:58, 6 February 2009
Line 1:		Line 1:
	~~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~~.		Dataflow is the fundamental concept under which the LabVIEW execution system executes code written in G (the graphical language used in LabVIEW). 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 nodes (functions, structures, and subVIs) have inputs, process data and produce outputs. Whenever all of a node's inputs contain valid data, that node will be scheduled for execution by the LabVIEW execution engine.  As soon as a processor becomes available (subject to available CPUs and the completion of previously scheduled nodes), the node will be executed.

	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~~.		By chaining together nodes 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 a refnum data type.

	An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.		An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.

	== External links ==		== External links ==
	* [http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)
	* [http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)

	[[~~category~~:~~LabVIEW fundamentals~~]]		*[http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)
			*[http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)

			[[Category:LabVIEW_fundamentals]]

Michael_Aivaliotis at 09:00, 8 October 2007

2007-10-08T09:00:35Z

← Older revision		Revision as of 09:00, 8 October 2007
Line 4:		Line 4:

	An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.		An example of how dataflow works and how LabVIEW differs from textual languages is given in [http://www.cs.rpi.edu/research/pdf/99-5.pdf] this PDF titled ''LabVIEW and G as a Computing Language Course''.

	== External links ==		== External links ==

	* [http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)		* [http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)
	* [http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)		* [http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)

			[[category:LabVIEW fundamentals]]

Michael_Aivaliotis: Data Flow moved to Data flow

2007-10-08T08:55:09Z

Data Flow moved to Data flow

← Older revision	Revision as of 08:55, 8 October 2007
(No difference)

Pbrooks100: /* External links */

2007-07-09T21:29:04Z

External links

← Older revision		Revision as of 21:29, 9 July 2007
Line 7:		Line 7:

	* [http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)		* [http://en.wikipedia.org/wiki/Dataflow Dataflow] (Wikipedia Definition)
			* [http://en.wikipedia.org/wiki/Dataflow_language Dataflow langauge] (Wikipedia Definition)