Functional global variable - Revision history

Q at 15:01, 20 July 2021

2021-07-20T15:01:50Z

← Older revision		Revision as of 15:01, 20 July 2021
Line 1:		Line 1:
	{{TOCnestright}}		{{TOCnestright}}
	'''Functional Global Variables (FGVs)''' are ~~VIs~~ that ~~allow~~ controlled access to data or resources, often allowing various actions to be performed. Functional Globals most often make use of [[Uninitialized Shift Register]]s (USRs) or uninitialized Feedback Nodes as the mechanism to store data. USRs are [[Shift Register]]s that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.		'''Functional Global Variables (FGVs)''' are a [[Design Patterns\|design pattern]] used in a [[VI]] that allows controlled access to data or resources, often allowing various actions to be performed. Functional Globals most often make use of [[Uninitialized Shift Register]]s (USRs) or uninitialized Feedback Nodes as the mechanism to store data. USRs are [[Shift Register]]s that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

	==Alternative Nomenclature==		==Alternative Nomenclature==

Q: Combined information from design pattern page

2020-06-03T18:51:56Z

Combined information from design pattern page

← Older revision		Revision as of 18:51, 3 June 2020
Line 1:		Line 1:
	{{TOCnestright}}		{{TOCnestright}}
	Functional ~~Globals~~ are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals ~~(FGs)~~ most often make use of ~~uninitialized shift registers~~ (USRs). USRs are ~~shift registers~~ that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.		'''Functional Global Variables (FGVs)''' are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals most often make use of [[Uninitialized Shift Register]]s (USRs) or uninitialized Feedback Nodes as the mechanism to store data. USRs are [[Shift Register]]s that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

	==Alternative Nomenclature==		==Alternative Nomenclature==
	Functional Globals are known by various names among LabVIEW programmers.		Functional Globals are known by various names among LabVIEW programmers.
	*LV2 globals – because LV2 supported uninitialized shift registers
	*USR globals – since most FGs make use of uninitialized shift registers		* LV2 globals – because LV2 supported uninitialized shift registers
			* USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*Action ~~engines – it~~ has been argued ~~[http~~://forums.ni.com/ni/~~board~~/~~message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should~~ refer to ~~VIs~~ that just allow read/write access to data. Action Engines would refer to the larger set ~~of VIs~~ that allow some defined ~~action~~ on the data.		* Action Engine

			=== Action Engines (AEs) vs Functional Global Variables (FGVs) ===
			It has been argued that the term '''Action Engine''' should be used for this design pattern. The Action Engine (AE) design pattern can be thought of as a machine (Engine) that performs some useful task (Action) often on some data. <ref>Community Nugget 4/08/2007 Action Engines on NI Discussion Forums (https://forums.ni.com/t5/LabVIEW/Community-Nugget-4-08-2007-Action-Engines/td-p/503801)</ref>

			FGVs would then refer to a subset of AEs that just allow read/write access to data. Action Engines would refer to the larger set that allow some other defined actions on the data.

	The official name for these constructs in NI literature is Functional Global Variable~~, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated~~ that ~~Functional Globals is also~~ the ~~most popular choice~~.		The official name for these constructs in NI literature is Functional Global Variable (FGV) but understand that the names could be used interchangeably in other literature.

	==Structure==		==Structure==

Q: Category reorg

2020-06-03T17:25:45Z

Category reorg

← Older revision		Revision as of 17:25, 3 June 2020
Line 88:		Line 88:
	*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]		*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

	[[~~category~~:~~design patterns~~]]		[[Category:Intermediate Design Patterns]]

Pbrooks100: removed link to delteted "Action Engines" entry

2008-01-04T19:45:31Z

removed link to delteted "Action Engines" entry

← Older revision		Revision as of 19:45, 4 January 2008
Line 7:		Line 7:
	*USR globals – since most FGs make use of uninitialized shift registers		*USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*[[Action ~~engine]]s~~ – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.		*Action engines – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

	The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.		The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

Pbrooks100 at 12:07, 2 January 2008

2008-01-02T12:07:38Z

← Older revision		Revision as of 12:07, 2 January 2008
Line 7:		Line 7:
	*USR globals – since most FGs make use of uninitialized shift registers		*USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*[[Action ~~Engine~~]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.		*[[Action engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

	The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.		The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

Pbrooks100 at 12:07, 2 January 2008

2008-01-02T12:07:17Z

← Older revision		Revision as of 12:07, 2 January 2008
Line 7:		Line 7:
	*USR globals – since most FGs make use of uninitialized shift registers		*USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*[[Action ~~engine~~]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.		*[[Action Engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

	The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.		The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

Pbrooks100 at 12:03, 2 January 2008

2008-01-02T12:03:14Z

← Older revision		Revision as of 12:03, 2 January 2008
Line 7:		Line 7:
	*USR globals – since most FGs make use of uninitialized shift registers		*USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*[[Action ~~Engine~~]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.		*[[Action engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

	The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.		The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

Pbrooks100 at 12:02, 2 January 2008

2008-01-02T12:02:50Z

← Older revision		Revision as of 12:02, 2 January 2008
Line 7:		Line 7:
	*USR globals – since most FGs make use of uninitialized shift registers		*USR globals – since most FGs make use of uninitialized shift registers
	* VIG - "VI Global" as the VI performs the functionality of a global		* VIG - "VI Global" as the VI performs the functionality of a global
	*Action ~~Engines~~ – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.		*[[Action Engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

	The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.		The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

Michael_Aivaliotis at 10:51, 8 October 2007

2007-10-08T10:51:32Z

← Older revision		Revision as of 10:51, 8 October 2007
Line 88:		Line 88:
	*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]		*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

	[[~~Category~~:~~Design Patterns~~]]		[[category:design patterns]]

Jim kring: /* External Links */ changed Design Patters category to upper case to match actual category

2007-10-08T10:45:15Z

External Links: changed Design Patters category to upper case to match actual category

← Older revision		Revision as of 10:45, 8 October 2007
Line 88:		Line 88:
	*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]		*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

	[[~~category~~:~~design patterns~~]]		[[Category:Design Patterns]]