runtime error: "intersection set is empty"

Im in serious need of a grasshopper samaritan....

I have a set of surfaces I would like to remove from a larger surface but I always get the error "intersection set is empty" or it produces a surface with just one of the smaller surfaces removed instead of all of them. If anyone could help me I would be very grateful!!

Attachments:

Untitled.3dm, 55 KB
set is empty.ghx, 174 KB

Replies to This Discussion

Permalink Reply by Giulio Piacentino on September 26, 2010 at 10:31am

Hi Mickey,

is it possible that you are looking for a planar region intersection?
Have a look at the attached definition with just two components changed.
I hope this helps,

- Giulio
_______________
giulio@mcneel.com
McNeel Europe, Barcelona

Attachments:

setisempty-2.ghx, 178 KB

Permalink Reply by Mickey on September 26, 2010 at 11:10am

Hi Giulio,

Thank you for your help. Unfortunately what I'm after is the opposite of your solution so instead of a region intersection I need a region difference. However if I replace this function in the definition you sent me I end up with every variation of the original region with one of the smaller regions removed(see attached). How can I remove all the smaller regions from the larger region??

Thank you for your help Giulio!

Attachments:

setisempty3.ghx, 169 KB

Permalink Reply by Giulio Piacentino on September 26, 2010 at 2:04pm

I find it difficult to "explain" which parts to choose, too.
This is a possible working way (see attached).

With booleans I normally suggest students that it might take less time to just select the pieces manually, rather than trying to encode the logic into a definition. Unless the definition is really the point... :)

- Giulio

Attachments:

empty-is-empty.ghx, 317 KB

Permalink Reply by Mickey on September 27, 2010 at 3:13am

Hi Giulio,

I hadn't thought of creating a singular surface and splitting it, thank you very much! This solution will work perfectly for now. I need to apply my definition to a decent number of surfaces so I still need to crack the region difference and intersection commands. I came across this discussion last night which is exactly what I am trying to do unfortunately I don't know how to apply the solution as Im unsure of how my data structure should be organised.

http://www.grasshopper3d.com/forum/topics/curve-boolean-region

Permalink Reply by Giulio Piacentino on September 27, 2010 at 3:53am

I've forwarded your question to David Rutten, the developer of the region component and data flow. He can tell more about the data tree structure that is applicable to this case. Rhino exposes this functionality in another manner (through picking with _CurveBoolean).

- Giulio
_______________
giulio@mcneel.com
McNeel Europe, Barcelona

RSS