Broken Containment?

Hello, upon testing the containment of a grid of points and their inclusion within a series of bounding boxes it will it allow me to cull out points inside the boundaries (culling 1), and the points intersecting the boundaries (culling 0) thought it will not allow me to cull the points on the exterior of the boundaries (culling 2). Is anyone else running into this problem?

If there is a way passed this could some hints be sent this way?

Thanks.

Nick

Replies to This Discussion

Permalink Reply by Pep Tornabell on November 15, 2010 at 6:04am

Once you have culled he inner and intersectiong points, you can invert the culling pattern to have the outer points... this might work

Permalink Reply by Laurenz Charles on February 19, 2011 at 6:12am

I am having the exact same issue, and reversing the pattern does not cull the exterior points. This is surely because I am using multiple containment inputs (with a graft), but I have not figured out how to manage the lists effectively to select the points that are not contained. Any input here would be greatly appreciated.

Attachments:

Permalink Reply by Chris Tietjen on February 19, 2011 at 7:44am

Chris

Permalink Reply by Laurenz Charles on February 20, 2011 at 3:47am

Thanks Chris,

Do you think that this can be done by using one curve container with multiple referenced curves? Imagine if the definition used 100 boxes instead of 2. This is the list management problem that I am having with on the definition above.

Cheers.

Permalink Reply by Chris Tietjen on February 20, 2011 at 5:59am

Laurenz,

I couldn't get the definition to work with multiple containment curves in one parameter. It seems like it should work that way so it may be a bug but it may also just be the limitation of the component. It could also be that we're not using it correctly. Hopefully someone else will be able to comment on this for clarification.

Chris

Permalink Reply by Laurenz Charles on February 20, 2011 at 8:27am

Thanks for the efforts anyway Chris...

I will post a clean definition when I figure out a work around...

Permalink Reply by Nicholas Pajerski on February 20, 2011 at 11:27am

All,

The problem is that the component recognizes each curve alone thus resulting in a series of overlapping data to cull when grafted. The solution posted is not the most elegant (having to weave culled lists) but does work if you understand the limits of your definition at the time. Would be easier written VB allowing for change in inputs I bet but here is a temp solution.

Best,

Nick

Attachments:

Permalink Reply by Laurenz Charles on February 20, 2011 at 11:47am

Beautiful... Many thanks Nick, this is a true help!

Permalink Reply by Andrew Heumann on February 20, 2011 at 12:41pm

Here's a solution that works for an arbitrary number of bounding curves without any weaving or definition modification required.

Attachments:

NotContained_2.ghx, 108 KB

Permalink Reply by Laurenz Charles on February 20, 2011 at 1:16pm

Even better yet! This is the exact list management trick that I was looking for.Though seemingly simple, I seriously would have never thought of it...

Brilliant!

Permalink Reply by Chris Tietjen on February 20, 2011 at 1:54pm

Very instructive. Thanks Andrew.

Chris

Permalink Reply by Stephen Foley on June 14, 2011 at 9:47am