Area comp taking way too long to solve?

Replies to This Discussion

Permalink Reply by David Rutten on July 15, 2013 at 3:40pm

Are your surfaces very big compared to your Rhino document tolerance?

--

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by Ron Shvartsman on July 15, 2013 at 4:11pm

Thanks for you speedy reply David. I assume your referring to the relative and absolute tolerances (image attached)? Is this what your talking about? The object I am working on is a building (massive airport). I have never had a problem before though.

Attachments:

• Capture.JPG, 83 KB

Permalink Reply by David Rutten on July 16, 2013 at 1:43am

Yes, specifically the absolute tolerance.

However from your image it seems your tolerances are not untoward. 0.01 while modeling in meters should be ok.

Area and Volume computations are remarkably slow though, I've noticed this before. Can you cut down your file to just the surfaces in question (you can internalize them) and the Area computation so I can have a look at the problem. Also please post the 3dm file so I can duplicate your exact tolerance settings. The 3dm file can be empty otherwise.

--

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by Ron Shvartsman on July 16, 2013 at 12:58pm

Thank you for your help David. Looking forward to hearing back from you about what the problem may be.

Attached...

Attachments:

• Area Comp Test File.3dm, 403 KB
• Area Comp Test File.gh, 80 KB

Permalink Reply by Steve Lewis on July 16, 2013 at 3:25pm

Maybe unrelated, but this is an issue i raised over a year ago with regards to speed of calculating areas using my .net code. i believe rhinocommon was updated so that a speedier solution was obtained by exposing a new rhinocommon method of calculating area that is not obtained form the areamass method. I believe this new area method on a brep in rhinocommon is much much faster than the area mass property method. Maybe newer update of gh is not using this method? Just a thought.

Permalink Reply by Dekani Fisher on November 28, 2013 at 10:30am

Hi guys. I've worked out that if you rebuild the surface being plugged into the area component with a low U and V number then the area component seems to work much quicker. (if you're using the sort component after then put your original surface into the 'k' input)

Permalink Reply by Firat Aydin on February 20, 2017 at 5:55am

can you send a sample code or GH definition ?

Thanks...