I am trying to create faired hull lines. I have to fair in 3D. To go from frames to waterlines, I have been extruding a set of horizontal lines and intersecting. I do the similar to get go to buttocks and back to frames.
The problem I am having is that this process is creating inconsistent points due to errors. The amount of different is tiny so I could ignore it if only I could get rid of duplicate point. SelDup is not finding pairs like this:
point
ID: 5390e34c-2b55-424b-93a8-98928a1a836f (308724)
Layer name: Stern Frame Points 3
Render Material:
source = from layer
index = -1
Geometry:
Valid point.
Point at (796.0000000,15.2718439,24.0000000).
point
ID: a688aa66-a381-4350-9262-876cd23056e4 (313039)
Layer name: Stern Waterline Points 3
Render Material:
source = from layer
index = -1
Geometry:
Valid point.
Point at (796.0000000,15.2718489,24.0000000).
These are so close that it does not matter which duplicate I get rid of. Is there any way to find duplicates within a tolerance?
You can try running the following script. Just save it somewhere and then use RunPythonScript to run it. Will default to finding points within the current file tolerance, but you can set the tolerance level anywhere you want at the command prompt.
Yeah, it is pretty handy in making your own tools or ones that Rhino hasn’t gotten around to integrating yet. It’s not an instant learning curve, but the effort put in is worth it IMO. You’ll wonder how you managed without afterwards.
That being true, it is still way, way easier to write scripts on Windows Rhino than in Atom. Not that I’ve done a lot with Atom, preferring the path of least resistance in this case.
True enough, I do all my development in Windows and just test on Mac. Atom is better than nothing, but I find it somewhat hard to get used to relative to the Windows scripting interface, and the lack of a debugger is what really kills it. I think I have learned more about how python scripts work just by inspecting what is happening in the debugger than anything else.