Accepted Solutions
OK, here are two suggestions of mine. They expect a (nested) n x 1 vector of points as ínput and also return that kind of structure as output. So you have to transpose your input row vector when you feed it into the functions and also have to transpose the result to get the row vector which (for reasons unknown to me) you want to get. I would rather use n x 1 nested vectors throughout (after all its the structure also needed for the 3D plot) and would only transpose them when displaying them to save vertical space. But of course thats up to you.
@lvl107 seems to be a colorful person who likes colorful plots. From his previous postings I got the impression that if he plots a couple of points, his goal is that each of them could be colored individually and if he plots an object in 3D like a polyhedron, he wants to be able to assign every side panel its own color (and transparency,...). Similar to what can be seen here: https://community.ptc.com/t5/Mathcad/Polyhedron-quot-28-quot/m-p/822519/highlight/true#M202526. Thats the reason for the blown up multiple nested matrices.
Deleting duplicates as demanded in this thread is not difficult that way but dealing with that kind of multiple nested structures can be quite a hassle normally. In the past I also suggested using a different structure like the one you proposed and also provided functions which enabled to switch between the different structures. At least for point lists. The nested structures used to plot 3D surfaces are not that easy to deal with - especially, it is hardly easy to join different surfaces into a single one and back, like we can do easily with points. Actually its a big drawback that we can't use NaN's in a MC15 3D plot like we can do in the 2D plots. Thats one of the few improvements in Prime, but then the 3D plot in Prime generally is ... (hmmm, I can't think of a polite way to put it right now)
Hi,
Firstly refuse to deal with the nested array structure three deep you use for the points definition.
I usually deal with 1000's of points in one array.
Here is solution with simpler coordinate definition structure.
Cheers
Terry
BTW, your "Equate" function could be simplified to
But I guess its more comfortable to transpose the input matrix, use the column selector and transpose the result:
OK, here are two suggestions of mine. They expect a (nested) n x 1 vector of points as ínput and also return that kind of structure as output. So you have to transpose your input row vector when you feed it into the functions and also have to transpose the result to get the row vector which (for reasons unknown to me) you want to get. I would rather use n x 1 nested vectors throughout (after all its the structure also needed for the 3D plot) and would only transpose them when displaying them to save vertical space. But of course thats up to you.
@lvl107 seems to be a colorful person who likes colorful plots. From his previous postings I got the impression that if he plots a couple of points, his goal is that each of them could be colored individually and if he plots an object in 3D like a polyhedron, he wants to be able to assign every side panel its own color (and transparency,...). Similar to what can be seen here: https://community.ptc.com/t5/Mathcad/Polyhedron-quot-28-quot/m-p/822519/highlight/true#M202526. Thats the reason for the blown up multiple nested matrices.
Deleting duplicates as demanded in this thread is not difficult that way but dealing with that kind of multiple nested structures can be quite a hassle normally. In the past I also suggested using a different structure like the one you proposed and also provided functions which enabled to switch between the different structures. At least for point lists. The nested structures used to plot 3D surfaces are not that easy to deal with - especially, it is hardly easy to join different surfaces into a single one and back, like we can do easily with points. Actually its a big drawback that we can't use NaN's in a MC15 3D plot like we can do in the 2D plots. Thats one of the few improvements in Prime, but then the 3D plot in Prime generally is ... (hmmm, I can't think of a polite way to put it right now)
