I need to keep the holes in the same position as in the Boundary Surfaces. I don’t know why my data structure is a mess. I pulled the curves, lofted, countour, boundary surfaces, extrude and solid difference.
banco parametrico.gh (28.3 KB)
I can’t internalize it. I’m importing some control point curves from Rhino. Is there a way I can do it anyways?
right click on this and chose “internalise data”
after that, do the same also with the other component
then save the gh file with different name and reupload it
GH BANCO FORUM.gh (32.0 KB)
there are many examples in this forum on how to nest the proper way using opennest, consider also upgrading to opennest_2, which would make things a bit easier
I’m using opennest_2 so I can only give you some hints, but the general thought is always the same: once you have succesfully created your slices as Surface of what you want to nest, you just nest their outer curve, and use the opennest Transform data to get the final result
so, these are the Surfaces you want to Nest:
everything that happens to the left of this component is irrelevant for the nesting operation, and for the next time you could just internalize those
this is a generic setup:
GH BANCO FORUM_inno.gh (401.5 KB)
A) put the curves on XY (maybe unnecessary step as they aleady lie on XY at different Z…)
B) get Surface edges, Join them in all closed curves
C) sort those curves by their length: longest first
D) pick just the longest curve (which we assume is the outer boundary) and use it for nesting
#) OpenNest generates a list of transform data: one transform for each outer curve
E) Apply those transform data not just to the outer edge, but to whatever belongs to a given surface, including the inside holes
I noticed that there are some intersections.
I don’t know if it’s due to my version of Open Nest.
I tried to solve the problem this way.
For convenience I used a Pufferfish component, but you can use Bounding Box.
the problem with that approach is that you won’t take advantage anymore of any cavity a shape has, which translates into waste of sheet area
I reverted my opennest_2 installation to 1.5 to see what’s going on, the problem comes from the nesting curves not having a good point distribution
so, for instance, even if you visualize on-screen that you are nesting these:
Opennest 1.5 is nesting these:
by doing that, the “backbone” of the nesting looks fine:
but when you use transform data to put the original curves back, you might get the intersections you mentioned:
to solve this it’s sufficient to pass the nesting curves into a ToPoly with a well weighted Tolerance, for instance:
GH BANCO FORUM_inno_ToPoly.gh (403.7 KB)
this allows you to take advantage of nesting concave shapes together and save 20%+ sheet area, but costs some more nesting time
as a side note, same set of geometries, simpler setup, and OpenNest_2 is so much faster:
1 Like