State Machine Actor - Revision history

Q: Added link to applicable toolkit on VIPM.io

2021-02-17T02:23:46Z

Added link to applicable toolkit on VIPM.io

← Older revision		Revision as of 02:23, 17 February 2021
Line 38:		Line 38:
	=== Stop Core ===		=== Stop Core ===
	[[File:SMA-Stop Core.png\|467x467px\|frameless\|center\|Stop Core]]		[[File:SMA-Stop Core.png\|467x467px\|frameless\|center\|Stop Core]]

			== External Links ==
			* [https://www.vipm.io/package/ni_lib_state_pattern_actor/ NI State Pattern Actor by NI (VIPM.io)]

	[[Category:Actor Oriented Design Patterns]]		[[Category:Actor Oriented Design Patterns]]
	[[Category:Actor Framework]]		[[Category:Actor Framework]]

Q: Category reorg

2020-06-03T16:26:37Z

Category reorg

← Older revision		Revision as of 16:26, 3 June 2020
Line 39:		Line 39:
	[[File:SMA-Stop Core.png\|467x467px\|frameless\|center\|Stop Core]]		[[File:SMA-Stop Core.png\|467x467px\|frameless\|center\|Stop Core]]

	[[Category:Design ~~patterns~~]]		[[Category:Actor Oriented Design Patterns]]
	[[Category:Actor Framework]]		[[Category:Actor Framework]]

Q at 00:27, 3 December 2018

2018-12-03T00:27:48Z

← Older revision		Revision as of 00:27, 3 December 2018
Line 1:		Line 1:
	The '''State Machine Actor (SMA)''' [[design pattern]] is completely implemented in Messages, it does not override the Actor Core. It sends the first Message on Pre Launch Init Method. Each subsequent Message sends the next Message in the state.		The '''State Machine Actor (SMA)''' [[Design Patterns Overview\|design pattern]] is completely implemented in Messages, it does not override the Actor Core. It sends the first Message on Pre Launch Init Method. Each subsequent Message sends the next Message in the state.

	Because it doesn't override the Actor Core the pattern does not have a UI of its own. It could be paired with another Actor that implements the UI and sends Messages to it to update UI elements. The paired Actor would follow one of the other patterns.		Because it doesn't override the Actor Core the pattern does not have a UI of its own. It could be paired with another Actor that implements the UI and sends Messages to it to update UI elements. The paired Actor would follow one of the other patterns.

MichaelAivaliotis: wikified some text

2018-11-11T22:13:42Z

wikified some text

← Older revision		Revision as of 22:13, 11 November 2018
Line 1:		Line 1:
	The '''State Machine Actor (SMA)''' design pattern is completely implemented in Messages, it does not override the Actor Core. It sends the first Message on Pre Launch Init Method. Each subsequent Message sends the next Message in the state.		The '''State Machine Actor (SMA)''' [[design pattern]] is completely implemented in Messages, it does not override the Actor Core. It sends the first Message on Pre Launch Init Method. Each subsequent Message sends the next Message in the state.

	Because it doesn't override the Actor Core the pattern does not have a UI of its own. It could be paired with another Actor that implements the UI and sends Messages to it to update UI elements. The paired Actor would follow one of the other patterns.		Because it doesn't override the Actor Core the pattern does not have a UI of its own. It could be paired with another Actor that implements the UI and sends Messages to it to update UI elements. The paired Actor would follow one of the other patterns.

Q: Added content from the FANDOM site.

2018-11-11T20:54:21Z

Added content from the FANDOM site.

New page

The '''State Machine Actor (SMA)''' design pattern is completely implemented in Messages, it does not override the Actor Core. It sends the first Message on Pre Launch Init Method. Each subsequent Message sends the next Message in the state.

Because it doesn't override the Actor Core the pattern does not have a UI of its own. It could be paired with another Actor that implements the UI and sends Messages to it to update UI elements. The paired Actor would follow one of the other patterns.

== Collatz Sequence ==
Below is an example of the SMA pattern, of where the Actor has an Initialization and three States which solve the Collatz Sequence. The Collatz Sequence is a sequence of positive numbers given any starting number where the next number in the sequence is calculated by:
n --> n/2 (n is even)

n --> 3n+1 (n is odd)
The sequence always finishes when n = 1.

== Code ==
Translating the Collatz Sequence into these states creates:
* State 1 checks ''n'' for even or odd, then decides to send State 2 or State 3 Messages
* State 2 calculates ''n/2. ''If ''n = 1'' the send Stop Message, else send State 1 Message
* State 3 calculates 3''n+1. ''If ''n = 1'' the send Stop Message, else send State 1 Message
The final sequence would be sent with the Handle Last Ack, if launched as a nested Actor. However, in this case the launcher started a User Event and is waiting for the final sequence. The Stop Code is overridden to send the User Even.

=== Launcher ===
[[File:SMA-Launcher.png|700x700px|frameless|center|Launcher]]

=== Pre Launch Init ===
[[File:SMA-Pre Launch Init.png|558x558px|frameless|center|Pre Launch Init]]

=== Initialization State ===
Most of the time this code should be handled in the Pre Launch Init. Another initialization step might not be necessary.
[[File:SMA-Init.png|611x611px|frameless|center|Initialization State]]

=== State 1 ===
[[File:SMA-State 1.png|776x776px|frameless|center|State 1]]

=== State 2 ===
[[File:SMA-State 2.png|700x700px|frameless|center|State 2]]

=== State 3 ===
[[File:SMA-State 3.png|700x700px|frameless|center|State 3]]

=== Stop Core ===
[[File:SMA-Stop Core.png|467x467px|frameless|center|Stop Core]]

[[Category:Design patterns]]
[[Category:Actor Framework]]