Hi there
I want to exclude some values from d when it is bigger than the width .... I want the program to just exclude the values that do not fulfil the condition, I used this program ,but it shows strange error ...I'm sure both of them have the same units
How to fix this ?
Maybe now we are back to the subject of this thread as i think that you not only want to delete some valued from the min-distance vector but you also would like to keep the corresponding point coordinates as well.
So I modified my "exclude" function to work on matrices. You have to provide the column index of the column you want the boolean function to be applied to.
Given that matrix
and applying this boolean function
to column 6 ("distance"), we get
To get rid of the header we can modify the boolean function
Now you could plot all C-points (green) with a minimum distance to A greater or equal as width (45.3 m).
The reason for this undesired zoom chosen by the plot is that the origin is one of the C.points. I am not sure if this is as it should be.
So to get something more visually appealing we again have to manually change the axis limits
One thing I noticed is that the number of entries in your "result3" and in my "raw" differ significally!
This could mean that my way of calculating the minimum distance in getNearest might be wrong?!?
You'll have to double check. I did not bother follow up to look where the vector d would come from, etc.
Your sheet definitely needs a heavy cleanup, I think.
EDIT: Just noticed that you uses <= in your boolean function while I used <. But this seems to have no effect anyway because there seems to be no min-distance of exactly 45.3 m.
Hi Werner,
Thank you for your reply.
I think the reason I get different numbers in (result3) is because I changed the equation I wanted to spot the selected and you spot the excluded values >> both of them works for me .
for the plot is incredibly impressive and showed we are in the right track.
However, why do you think my plot looks different than yours?
@YA_10963798 wrote:
Hi Werner,
Actually what I need is to show in the plot all the points and then color the ones we selected which there distance is less than 45.3m in different color.
So it is easy for anyone to grab the idea that there is this amount of CPTs are exlculded from the plot rather go to check each single distance.
in the new plot it is okay if we don't show the distance , but I need to show the one selected. So, let's say A points in blue, Exclued C points in red and the rest of point C in green. Is that possible?
Thanks @Werner_E
Yes, and you actually already did in your plot.
After choosing a Symbol for each plot as you already did you simply have to change the line style to "none" so that only the points are plotted without connecting them.
And then color the second and the fourth plot in blue as these are the A-points corresponding to the plotted C-points.
That way only the 2028 A-points which correspond to one of the C-points are plotted.
If you need to plot all 3146 A-points, you simply delete the second and fourth trace and plot second column of A over first column of A as a third plot.
Your points are quite close to each other so in a plot which shows all of them the points will overlap.
One has to be careful concerning the order the traced are created. The last plot will overlap the others and I found no way to change that order (other than redoing the plot from anew).
As already written above, the data for C.CPT includes the origin (0;0). This is the reason why Prime choses the zoom in a way so that this point is included in the plot, resulting in the main data to be shown very tiny at the upper right.
As i thought that its not as intended that the origin is part of the c points, I investigated and found that the origin is part of the C data not once but even nine times at different rows.
In the attached sheet I got rid of these entries by using the trim command
You used absolute values when you used the submatrix command. As table2 would have a lower number of rows now, this command would fail. I changed it to be aware of the row number of table2.
Now that the origin is not part of the dataset anymore, Prime automatically chooses a more appropriate zoom and we don't have to manually 'zoom' by changing the axis limits
or that way
Prime 9 sheet attached
