I was trying to make a little customization to the original MeshMachine code (by @DanielPiker) in python. The original code utilizes the plankton (by @will) library, which I managed to port into python and got it to work. While sometimes it fails when doing Pmesh.Compact() and ends up with a mesh missing several triangles. I couldn’t figured out what is happening under the hood.
Then I find that in Rhinocommon, the MeshTopologyEdgeList class has three similar methods, “CollapseEdge”, “SplitEdge” and “SwapEdge”. I would like to know how these methods affect the original indices for Vertices, TopologyVertices and TopologyEdges. For example, when a topologyEdge is collapsed, does the indices for the rest of the topolgyEdges shift ahead in order?
Thank you in advance,