Hello everyone,
It would be greatly appreciated if you could please help me to find the fastest way to split the list of closed curves (297,000 items) by curve.
I have tried different ways, converting the curves to a mesh and working with mesh splitting, but it is still taking a long time and ending up with the error “Rhino is out of memory”.
Thank you so much for any help you could provide 
Spliting the tiles.gh (59.8 KB)
This is not enough effort on your part.
The definition is going to be really slow if you offset all the squares and equalateral triangles after tiling them. Instead, offset the repeating tile before arraying it. Both this and how to trim the pattern to a boundary are shown in your previous thread. You may have to reach for other method for trimming the pattern if Region Intersection becomes too heavy, such as collision detection to first roughly reduce the pattern to the shape of the contour.
Thank you for your quick reply! I don’t have much experience, but I’ll try to select the curves that intersect with the splitting curve first
I’m afraid this might cost me another half day, if you remember similar case, please share the thread.
Thank you un advance!
Check your scale! The tiles have a side length of 1 to 10, but the contour is, what? 200,000 units across?
The model is set up in mm, and the tile size is 500 mm.
The length of the boundary area is around 300 m.
You said you were going to “try”, you tried for a whole 7 minutes before saying it’s taking too long…
Anyway, I would not use Mesh Split and instead use Project Curve - use Boundary Surfaces to make your outline into a planar surface to project the curves onto.
I would take the Area Centroids of each tile first though and check that they’re within the boundary first, that way you’ll have fewer curves to project.
I would also recommend making your tile size like 50x bigger - once the script works with 100 objects, you can reduce the tile size and leave your computer to calculate the whole 300k, troubleshooting a script that you can’t even run is pointless.
Thank you for your reply. I was answering in 7 minutes, as i’m on it already the whole day, it wasn’t 7 minutes. I tried spending time to solve it before writing here, but it wasn’t successful, and I have pressure because of the deadlines. But never mind, I’m thankful for all the feedback I can receive from you guys! Thank you again
Your boundary curve is floating is space. Bring it to the XY plane.
Tip of the Day. Try offsetting or doing anything involving boolean regioning in this plug-in and it makes you want to throw your computer out the window.
Just for comparison:
Trim with Region: 3.2 minutes
Project Curve: 17.9 seconds
Clipper2 Boolean 2.2 seconds
Decagon Grid VR10.gh (87.4 KB)
Thank you so much for providing the script, it is very helpful!
