LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Graphic problem 3d - can't show all my data

I have a problem, I want plot my data to a 3D graph, but not all datas were show in the plot.
 
For example A421;21;14;4 or A55;4;4;4 don't show these datapoints in the plot, but others shown.
 
Have anybody an idee what I can do with these problem ??
 
I've done the VI an the csv data as an attachment
 
I have LV 8.21 
 
thx for your help
Download All
0 Kudos
Message 1 of 11
(3,529 Views)
Part of your problem is in the data itself. The way you have it programmed you are assuming elements are separated by semicolons. You have values in Column B. Are they supposed to be there? Also, what is #NV supposed to represent? I assume this is "no value", or something like that?

Tip: You do not need to transpose the array. Instead of wiring to the "row" input of the Index Array, just wire to the "column" input. Same difference.
0 Kudos
Message 2 of 11
(3,520 Views)

The values in Column B are the coordinates  from x, in C the coordinates from y  --- and D the coo. from Z (normally I have more z datas, but I want clear the problem with one data)

How do I change the datas ?? - Do you mean ist isn't good do save it with separated by semicolons??

#NV = no value  .. but I think LV is it equal that I write

 

But why LV don't show the points from (x/Y)  For example (21;14) or (4;4)   but  (21;16) or (21:15) ???  it's logic ?? 

0 Kudos
Message 3 of 11
(3,510 Views)
I never said that using semicolons was wrong. It's perfectly fine. I was simply pointing out that you're using semicolons, and some lines had extra "stuff". When I open the file in Excel I don't get the coordinates from X in column B, etc. I get, for example, "A1;0;7;#NV" all in column A. The line with A56 is actually "A56;4;5;3,5" in the csv file. In Excel, the last 5 is put in column B.

That said, that's really more of an Excel issue. In your particular case, for example, the "A55" line is actually "A55;4;4;4,", so when you read it into LabVIEW, the "Z" value is "4,". Notice the extra comma. The plot interprets this the same way as #NV, and doesn't plot it. Another example: the "A96" line. The line in the file is actually "A96;6;4;3,5". When you read it into LabVIEW the "Z" value is "3,5". The plot doesn't know how to plot this.

If you intend to plot more than one "Z" value for the same X,Y coordinates they should either be on separate lines, or you need to parse the string that is the "Z" value so that you generate an addition X,Y,Z point for the plot.
0 Kudos
Message 4 of 11
(3,493 Views)

Your data is there. Do the following steps to see the data points: go into the properties of the 3D graph, select the Plots tab and then the Style tab within that. Change the plot style from "surface" to "Point". Now, click the Edit button next to the Color map style. In the color map editor, change the color for the zero value to white instead of the default black, change the color for the highest value to black from white and click OK.

Now, select the "Projection" tab for the plot and turn on projections for all three planes. Also turn on "Only show projections". Click 'Apply'.

This will expose all of your data points that have z > 0.

In the preview window for the 3D graph, you can see that the data points 4,4,4 and 21,14,4 do exist in the graph.

The problem is that when you change the plot style from 'Point' to any of the other styles, these particular points seem to vanish. To me, this appears to be a fundamental issue with the 3D graph control.

0 Kudos
Message 5 of 11
(3,488 Views)
"... these particular points seem to vanish. "
 
Without looking, could that be a near field clipping issue?
 
Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 11
(3,485 Views)
For the data point 4;4;4 this could be the case. There is a point very near it that has z = 35 (this is A56;4;5;3,5). This point is so tall that it consumes the one near it.
However, the points at 21;14;4 and 21;16;4 have the same small height and look like they should not interfere with each other.
I also noticed that all of the entries that have #NV for the z value, are interpreted as z = 0 and they appear in the graph as well. I would think that this data should be stripped out before sending the array data to the 3D graph.
0 Kudos
Message 7 of 11
(3,478 Views)

I am eddie123_berlin

 

Give it a chance to plot all points with another style as point ??

I found the style surface very good, but I havn't all points which I measured.

And I don't understand how can I show one point, and another not which is one point between.

 

0 Kudos
Message 8 of 11
(3,469 Views)
To eddie123_berlin,
 
my original reply to you was just to prove that all data is making it into the 3D graph control. I agree that the style 'surface' would be the preferred style. I think that the problem is with the 3D graph control and not with your program. I could not find any property settings that would fix this.
 
I took your data and deleted all of the rows that had #NV for the z value. After that, I ran the program again and got a much different surface plot. This also allowed the data point 21;14;4 to show up next to 21;16;4.
0 Kudos
Message 9 of 11
(3,466 Views)
 
Ok, I believe also that their are problems with the 3D graph control that they can't show the plot-points correctly.
And if I deleted all of the rows that had #NV  ... the plot is very expended as the original, so I can't do that, but now I can see some data-points which I don't see before.
 
 
 
 
 
 
0 Kudos
Message 10 of 11
(3,459 Views)