Jump to content

User group: Difference between revisions

From LabVIEW Wiki
Line 46: Line 46:
!|SME Requirements
!|SME Requirements
|-
|-
|Team Based Development with LabVIEW
|What to Expect When You're Expecting an Error
|This session will provide an overview of best practices and tooling that should be used to streamline LabVIEW development by a team of developers
|Connecting error wires across nodes on a block diagram is one of the most common, brainless tasks performed by a LabVIEW programmer. Unfortunately, this often means that VI behavior in an error condition is a second thought, if it's even thought about at all. This presentation will cover best practices in regards to the generation and propagation of errors on LabVIEW block diagrams. You should come out of this presentation with the ability to write VIs that are not only functionally correct in an error condition, but also precisely convey their exact error behavior in an error condition.
|Elijah Kerry
|Darren Nattinger
|Slides [https://forums.ni.com/ni/attachments/ni/7305/836/1/Source%20Code%20Control%20-%20Managing%20Applicaiton%20Development%20with%20the%20LabVIEW%20Project.pptx Team Based Development in LabVIEW]
|Slides [http://bit.ly/dnatterrors]
|Yes - CLA-level knowledge of how to manage and coordinate development activities across a team
|Yes - CLA-level knowledge of how to manage and coordinate development activities across a team
|-
|-
|}
|}


==References==
==References==

Revision as of 00:42, 4 April 2024

A User Group, or LabVIEW User Group (LUG), is a local group of LabVIEW enthusiasts that come together to share common interests or goals. The user groups within the NI Community are segmented into different categories such as Local User Groups, Product User Groups, Special Interest Groups, and Partner Groups. Within each of these groups, you may collaborate with others on best practices, plan in-person meetups, or discuss any topic of your choice. [1]

Organizing a User Group

User groups are typically created out of a shared need to seek advice and share ideas among a community of individuals that are working on similar problems OR applications. It is recommended that such a group align on goals for the organization, such as the following:

  1. Share ideas and practices to improve the quality, performance, scalability and readability of LabVIEW code
  2. Provide a forum to solicit advice from peers regarding how best to solve technical and procedural challenges when developing LabVIEW code
  3. Drive standardization on stylings, code organization and tooling for the purpose of enabling greater reuse and collaboration

See the LabVIEW Community Forum: User Group List to find one near you.

User Group Content

This is a collection of content that can be used to organize and run a LabVIEW user group.

Best Practices

These presentations are intended to review best practices for code design and development processes. They are generally more advanced and benefit a presenter who has multiple years of experience with the relevant tools and technologies.

Presentation Title Abstract Author Demo Resources SME Requirements
Team Based Development with LabVIEW This session will provide an overview of best practices and tooling that should be used to streamline LabVIEW development by a team of developers Elijah Kerry GitHub Repo for slides and demo materials Yes - CLA-level knowledge of how to manage and coordinate development activities across a team
Using Plugin Frameworks for Extensibility This session will show how to improve the reusability and extensibility of LabVIEW code through the use of dynamically loaded plugins Elijah Kerry Example source code Yes - CLD-level knowledge of how to dynamically load and communicate with sub processes

Tips and Tricks

Presentation Title Abstract Author Demo Resources SME Requirements
What to Expect When You're Expecting an Error Connecting error wires across nodes on a block diagram is one of the most common, brainless tasks performed by a LabVIEW programmer. Unfortunately, this often means that VI behavior in an error condition is a second thought, if it's even thought about at all. This presentation will cover best practices in regards to the generation and propagation of errors on LabVIEW block diagrams. You should come out of this presentation with the ability to write VIs that are not only functionally correct in an error condition, but also precisely convey their exact error behavior in an error condition. Darren Nattinger Slides [1] Yes - CLA-level knowledge of how to manage and coordinate development activities across a team

References