07-19-2013 02:26 PM
@MrHappyAsthma wrote:
I understand the difference now, but I think I favor their approach.
If you have an array of clusters of arrays, you can reference each cluster by index as well. (To remove a whole row for example).
I don't believe there is any way to unbundle by index, is there? For example, remove array #2 from a cluster of 5 arrays?
Ah yes. There it is! And when your arrays are very big, you don't want many unbundles with only one connected terminal around. I see now. ![]()
07-19-2013 02:30 PM
I still cannot figure out how he made his array... I tried some stuff but it turns out much uglier than his haha:
07-19-2013 02:32 PM - edited 07-19-2013 02:34 PM
@MrHappyAsthma wrote:
I still cannot figure out how he made his array... I tried some stuff but it turns out much uglier than his haha:
I actually hate dealing with arrays/clusters on the front panel. Especially when you have an Array of Clusters of Arrays, there's so many different aspects of it to change.
I'd almost rather just have a bunch of single entry things and then build them into array/cluster/whatever…
07-19-2013 02:33 PM
I just try to avoid clusters period... I mean, I know C so its kinda like a struct. But the various functions and VIs on the pallette for the clusters just confuse me.
07-19-2013 02:39 PM
@MrHappyAsthma wrote:
I just try to avoid clusters period... I mean, I know C so its kinda like a struct. But the various functions and VIs on the pallette for the clusters just confuse me.
The right way would be to get familiar with the cluster tools to end the confusion once and for all. Right?
07-19-2013 02:44 PM
Thats the goal! But I learn best by seeing and then doing. But unfortunately no one has posted code to help me master the scary beast that is clusters.
I mean I've read through some of the basic documentation, but it barely scratches the surface. I know about as much as bundling and unbundling of data.
Once we start getting into multi-layered clusters and throw a few arrays in there as well... yeahhh... I get lost 😛
07-19-2013 03:12 PM
Well, a cluster is just a container that can contain all types of assorted things, even clusters. The elements have a defined order (that you can change). It is recommended to label the elements with logical names, so you can later access them by name for automatically self documenting code. Clusters often greatly simplify the diagram if you bundle things that belong together. One wire can replace a huge mess of wires.
Similarly, you put all your money in your wallet, all your gym clothes in the gym bag (sure you can just throw everything directly in the trunk of the car, but it will be more difficult to keep track of it all). You put all spoilable food in the refrigerator (and Inside the refrigerator, you have the veggies in the vegetable drawer, the milk and soda in the door, etc.).
07-19-2013 03:15 PM
Here ya go 😃 this is at least a starting place...
07-19-2013 04:58 PM
@altenbach wrote:
Well, a cluster is just a container that can contain all types of assorted things, even clusters. The elements have a defined order (that you can change). It is recommended to label the elements with logical names, so you can later access them by name for automatically self documenting code. Clusters often greatly simplify the diagram if you bundle things that belong together. One wire can replace a huge mess of wires.
Similarly, you put all your money in your wallet, all your gym clothes in the gym bag (sure you can just throw everything directly in the trunk of the car, but it will be more difficult to keep track of it all). You put all spoilable food in the refrigerator (and Inside the refrigerator, you have the veggies in the vegetable drawer, the milk and soda in the door, etc.).
Because one wire can replace a huge mess of wires, clusters are indispensible when using subVIs. Imagine unbundling your error clusters, for instance. If you did that, you'd be using six connectors instead of two!