Intersect and Dispatch Circles / Grid Cells

Hi Guys,

I intersected a rectangular grid with a series of circles, I would like to dispatch the grid cells which intersect with the Circles but can't find the right way to do it.

Would anyone know how to solve this?

Many thanks,

Arthur

Attachments:

Logo.ghx, 280 KB

Replies to This Discussion

Permalink Reply by David Rutten on August 25, 2010 at 2:25pm

Hi Evert,

there should be a difference between Preview On and Off components:

Are you not seeing this?

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Evert Amador on August 25, 2010 at 2:41pm

Whoops. I do now,

The difference is very subtle on my display, It doen's help neither that I usually use a 13" macbook.

Anyway thanks for clarifiying.

I don't seem to be able to show the remote control pannel, I can't select the option visible , I'm using 7.0048 on a macbook.

Cheers

Evert

Permalink Reply by David Rutten on August 25, 2010 at 2:52pm

Hi Evert,

the remote control panel is out for the time being. I'm rewriting it from scratch and it's taking longer than expected.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Danny Boyes on August 25, 2010 at 3:00pm

Hi Evert,

You can manually change this colour by opening the User Setting folder from the File menu and editing the XML document. The value you want to alter is the Hidden.Std.Fill (i think).

Permalink Reply by Evert Amador on August 26, 2010 at 2:25am

Hi Danny,

Thanks for replying I'll have a look at it.

David,

It would be really useful, at least for me, to have and options panel similar to rhino with viewing setting you can customise if that's possible.

Many thanks

Cheers

Evert

Permalink Reply by Danny Boyes on August 25, 2010 at 8:00am

I never thought of using the length of a list as a true or false generator. Thanks

Permalink Reply by Evert Amador on August 26, 2010 at 2:28am

I think this is really useful,

David, would it be possible somehow to have something similar to overload methods on components, I supposed they maybe are already there as it happens with what Danny mentioned, but maybe for others.

I don't know just a thought.

Cheers

Evert

Permalink Reply by Arthur Mamou-Mani on August 25, 2010 at 12:23pm

Hi David,

Thank you very much for your answer, it works perfect!

How are the two lines in the Path Mapper converting a list which has more than 5000path to one that only has 900paths while keeping the same tree structure and N numbers ?

Still having a bit of a hard time with this tool...

Permalink Reply by taz on August 25, 2010 at 12:54pm

Hey Arthur,

I didn't actually recreate David's definition, but it seems [CCX] is (potentially) outputing paths in 2 formats, {A;B} and {A;B;D}. The dual line path mapper simply deals with both conditions so the output is all formatted the same for either incoming path structure.

Permalink Reply by David Rutten on August 25, 2010 at 1:03pm

Hi Arthur,

the mapping {A;B;C} - {A;B} collects all data from all the possible C branches and places it into a master branch. It's basically like a localized flatten operation. Imagine the following Tree:

{0;0;0} N = 2

{0;0;1} N = 1

{0;0;2} N = 3

{0;1;0} N = 5

{0;1;1} N = 8

{0;1;2} N = 10

If we apply the aforementioned mapping to this tree, we'll end up with the following result:

{0;0} N = 6

{0;1} N = 23

Basically {0;0;0}, {0;0;1} and {0;0;2} are combined into a single path {0;0} as we disregard the third index because "C" is no longer present in the target mapping.

Because we only use the Mapper to modify paths, we do not lose any data items, though we might lose some of the paths.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Arthur Mamou-Mani on August 25, 2010 at 1:24pm

Thanks a lot ! Much clearer !

In the example below, the C branch is taken out yet the N values are not altered which was the case in the example you posted above, how does this happen ?

Also what would be the use of the second line in the mapping ?

Permalink Reply by David Rutten on August 25, 2010 at 2:23pm

Hi Arthur,

very observant. The second line in the mapper is what I call a null mapping, i.e. one that doesn't change the data layout.

However, that doesn't mean it's not doing anything useful. The data tree you're feeding into this PathMapper has certain paths in the form {A;B}, which cannot be handled by the {a;b;c} -> {a;b} mapping. When you create a Null Mapping Grasshopper will include this second line just to make sure that all paths will be handled and thus no data will be omitted during the mapping.

--
David Rutten
david@mcneel.com
Poprad, Slovakia