LabVIEW
different plots in one graph
Solved!
@Student_LV wrote:What I expect is spaced plots ( not too close as in the attached figure)
How can i provide a label for each plot, using property node, knowing that there are too many ones ?
The plot spacing is given by the data, not by the graph. You can show the visibility checkbox in the plot legend and hide some plots. All your traces seems similar. Maybe you could just graph the average of all. You could also display them as a surface in 3D.
@Student_LV wrote:
Hello!
I have a three-element-lisbox ( c1,c2,c3), where I can select more than one element, wired to the selector of a condition structure, for each case, there 's a sub VI in the condition structure relative to each case and the output of condition structure is a common XYgraph. In this case I can have the graph related only to one case (either C1, or C2 or C3), but what if the user select two elemnts from the list ( C1&C2 or C1&C2 or C2&C3 or even C1&C2&C3 )
That seems trivial. What have you tried? Can you show us your code?
This seems to be a completely different problem because you have more data sources and more different elements in the listbox. It would have helped to have some default data in the controls, but tehy are all empty. So the three Y arrays are all completely different data (all cases, specific, Cx, etc.)? Seems convoluted and misguided.
Still, maybe the attached will give you some ideas. I am sure it is not right, but the various cases show how to built the array of plots.
- Why are most of your front panel object indicators instead of controls? You are using them as controls in the code (via local variables).
- The legend visibility and number of rows needs to be set only exactly once so that belongs outside after the loop. If you would make the third case the default, you could even remove the "2..100". Case "0" should NOT be the default. The number of rows should be based on all plots, i.e. the size of the final array coming out of the shift register.
- Why are you using property nodes with explicit references? Is this called as a subVI?
- All terminals (or local variables) belong before the loop because they should be read only once unless you are expecting different values at different iterations.. You also only need to measure their sizes once.
- Should the lone outside property node execute before or after the loop? Define the order using data dependency!
- In the third case (2..100), the "active plot" needs to be [i] + 2.
- In the first case (1), you need to set the active plot to 1 before writing its legend.
Right now, your code just rolls down the hill once and stops a few milliseconds later. To make it interactive, it needs to keep running, so use an event based architecture where you re-run the current code of one of the critical inputs change and add other events where you look for cursor interactions and change the cursor name according to the active plot and cursor whenever it changes. Similarly, add a control and event to toggle legend visibility.
