Slow Region Interseccion

Replies to This Discussion

Permalink Reply by Danny Boyes on April 18, 2012 at 5:33am

How many circles and what is the data structure like?

• ▶ Reply

Permalink Reply by Óscar Herrero on April 18, 2012 at 8:46am

Danny, I'm goingo to reply you tomorrow, I don't have the file here. But thanks anyway.

• ▶ Reply

Permalink Reply by Óscar Herrero on April 19, 2012 at 2:11am

Hello Danny,

There are 81 circles, and I want to intersect them with other 81. The files is this:

It is better use regions or curves?

Attachments:

• circulos.gh, 18 KB

• ▶ Reply

Permalink Reply by Danny Boyes on April 19, 2012 at 2:50am

Hi Óscar,

Two things spring to mind here to fix this.

The most significant, you had Cross reference selected as the Data Matching option which since the introduction of data trees in GH has become obsolete. David might be making moves to remove this from components or make it obvious when it is being used in the near future.

The second point, In this particular case you have the same data order of each set of circles so there is only a need to make sure that each input has 1 circle per branch (only have graft on input B) so that it only needs to calculate the intersection of the pair not the possible intersections of every other circle on the surface.

These two items would bring processing time down considerably. It took my dual quad core xeon 20 seconds to process the unaltered file you sent. With the changes it took a fraction of a second.

Attachments:

• circulos_datamatchsolution.gh, 18 KB

• ▶ Reply

Permalink Reply by Danny Boyes on April 19, 2012 at 4:04am

I suppose I should amend this statement:

since the introduction of data trees in GH has become somewhat obsolete

• ▶ Reply