Jump to content

Search the Community

Showing results for tags 'data structures'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help


  • *Uncertified*
  • LabVIEW Tools Network Certified
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
    • Custom Probes
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website

Company Website

Twitter Name

LinkedIn Profile

Facebook Page



Found 1 result

  1. I have a list of circuit board input and output pins that I'm representing as 1D array of clusters with the following info: [Unique Identifier, Contact Description, Group, Top/Bottom of Board] Example: Example Data It seems to me like this would be a good case to use a Graph data structure. I've done the NI OOP training and am decently able to make my own, more simple classes. However, I really don't know how to use the Graph.lvclasses. This gives me the following questions: Is there a way other than a graph that's better for storing this data? I want to move to the Graph structure because I feel like it will give me the ability to more easily represent the complex connections on the board. Is there anything else that this format (or another) will help me to better do? Should I put this in an Access database instead and look at it with the database connectivity toolkit instead? I'm hesitant to do that as I have about 700 parts with 50 or so connections each. Putting all of that on to one table without any way I can think of to make a primary key feels like it could be a disaster ps - Apologies if this is too simple a question. I'm totally out of my depth here and, quite frankly, have no idea what I'm doing (Cue imposter syndrome ).
  • Create New...

Important Information

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