Grasshopper

algorithmic modeling for Rhino

Hello,

please look at the image.

As you can see i set up a simple "label displayer", showing the area of certain polylines.

what is really puzzling me is the behaviour described in the image:

you can see a comparison between "area" command from rhino and the area calculation from grasshopper.

What is astonishing is that...sometimes GH is wrong. REALLY REALLY wrong, not just a few decimal digits.

See the first half: Rhino says: 717,5 square meters, and GH says...717 (rounded) OK.

See the second half (same file, same everything): Rhino says: 113.9, and GH says... 11.9!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

how is that possible??? this makes this method totally unreliable, because sometimes is correct and sometimes not. what is the reason of this? how can i fix it?

thanx

Views: 2447

Replies to This Discussion

yes sir.

i also get the right values. sometimes.

this is the thing, it is not reliable, because knowing it could go nuts as in this case, every area has to be double checked (mostly just to know that the number is right, but in a fraction of cases......)

I understand that not having reliable results is a deal-breaker. It defeats the whole point of computation. I'd love to try and fix this bug, but I have to be able to repeat it first.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service