- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
EDQSM - producer-consumer based actor design pattern backed by a Mealy state machine
styrum
09-21-2018 12:26 AM - edited 09-21-2018 01:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
In connection with today's presentation I would like to show you one of my old design patterns (2006!) which, as opposed to MLA presented today, allows to keep overall structure of the code of every actor VI the same while the programmer fills it with specific functionality.
Key features beyond keeping the same structure and plumbing code regardless of the functionality of a particular actor:
- Separation of notions of events, states, and actions
- Separate queues for events and actions to facilitate Run To Completion scheduling
- State machine implementation where actions can be associated not only with entering a state but also with transitions between states (Mealy state machine)
- Isolation of the high level state machine logic (on which event in which state to run which actions and switch to which state) in a dedicated place in the code. This is worse than storing that information as a separate data structure and maybe even in a separate file editable with a specialized editor like it was done in my LabHSM toolkit but still much better than branching depending on the state in the actions themselves.
The original LAVA thread:
The code saved in LabVIEW 2016 is attached.
If you want me to do a presentation on this at one of the meetings, please let me know.
By the way, I am looking for a job right now.
So, here is my LinkedIn:
https://www.linkedin.com/in/stanislav-rumega/
With Best Regards,
Stanislav
