Jump to content

Actor Framework from NI Week 2010 presentation


Recommended Posts

[This message was also posted here on the ni.com forums.]

All of the presentations for NI Week 2010 are available in the NIWeek 2010 Community. If you attended NI Week, you should already be a member of the community. If you did not attend NI Week, click on the link and request to join the community (you will have to create a user profile if you have never used the NI Community pages ever before). Approval to join the community may take a day or so.

Once you are a member of the community, you can go here to get a full copy of the "LabVIEW Classes: The State of the Art" presentation that Mike Benza and I gave, along with all the VIs used during that presentation.

I spent the bulk of that presentation discussing my new Actor Framework.Many users have spent time developing mechanisms for starting up multiple top-level VIs, establishing communications among those VIs and then tearing those VIs down when the app completes. It is easy to make a system that works sometimes. It is very hard to make one that always starts cleanly (so no VI misses early messages), avoids deadlocks during communication, and actually shuts down all running processes. Very hard. Multiple users have posted their attempts to me.

At the same time, I've been looking at state machines, that very common design pattern for LV programmers, and lamenting that if I build one state machine for a project and then I need that same machine but with just one more frame of the case structure in another project, I have to copy all the code. How do I build a state machine that I can inherit from and extend?

These twin challenges lead to the development of the Actor Framework. It incorporates ideas from several similar frameworks developed by users (both internal and external to NI), and adds a few extras to make it really robust. I found one CLA who lives near NI to test drive the framework in a real-world application. That work is still ongoing, but so far, the framework appears to function well, with good performance and no missing functionality. More importantly, it is easy to pick up and learn -- we decided that was important since so many of the macroscale frameworks that have appeared in the last five years have a steep learning curve.

The framework should not be considered "finished". The presentation includes some notes about further refinements that we have planned, and I am open to further suggestions from the community. I would like to see this develop into something that we can share next NI Week as a polished set of VIs and classes that any of our users can pick up and run with.

Please post any comments you have about the framework on the community page where the framework can be downloaded. That way any conversation about it is centralized instead of being spread across the forums, LAVA and the NI Community.

PS: The Actor Framework is saved in LV 2009. You do not need LV 2010 to view and use the framework.

  • Like 2
Link to comment
The attached ppt was corrupted in my download. Anyone else have this problem?

I just tried downloading it again and it worked fine. Try again... I posted an update this morning... maybe you happened to be downloading during the exact 3 seconds when I was uploading the new version and something got confused.

Link to comment

Redownloaded and got the same error. Copied the file over to my flash drive and it works. Weird.

"The new features for LabVIEW 2011 will be a handful of very cool features (including a few from the LabVIEW Idea Exchange) and a huge number of bug fixes, editor performance upgrades and compiler optimizations. This decision comes in response to your user feedback."

Kudos to NI for making this call. :thumbup1:

Link to comment

"The new features for LabVIEW 2011 will be a handful of very cool features (including a few from the LabVIEW Idea Exchange) and a huge number of bug fixes, editor performance upgrades and compiler optimizations. This decision comes in response to your user feedback."

Kudos to NI for making this call. :thumbup1:

Where did you see this statement?

Link to comment

It's in the Notes section of my PowerPoint presentation. NI as a whole talked about this in the Keynote presentation.

Thanks. I assumed you were talking about LabVIEW Classes when I saw that section. I wasn't at NI Week this year, so I haven't seen the keynotes, yet. I'm hoping to get to view them this week, assuming I can find them on NI's website.

Link to comment

Redownloaded and got the same error. Copied the file over to my flash drive and it works. Weird.

"The new features for LabVIEW 2011 will be a handful of very cool features (including a few from the LabVIEW Idea Exchange) and a huge number of bug fixes, editor performance upgrades and compiler optimizations. This decision comes in response to your user feedback."

Kudos to NI for making this call. :thumbup1:

So stability will improve in 2011 right? Any chances of getting improvements in the 2010 SP?

Link to comment

So stability will improve in 2011 right? Any chances of getting improvements in the 2010 SP?

The SP is always a bug fix release, so I'm not sure what your question implies. We do shy away from significant refactoring projects in the SP because those do not go through the same deep beta process as a full release, but the major issues that we know about that have no workaround, we do address.

== Stephen

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.