Grasshopper

algorithmic modeling for Rhino

I've noticed that the bug for the catenary curve is still present when the model is using non metric units. For instance I cannot create a catenary curve if the model space is in units of in. If I use the same geomerty and component definition and change the model units to m - obviously making sure the model is also scaled at the same time- the catenry component will solve and give the correct geometry.

Views: 537

Replies to This Discussion

Hi Duck,

 

it's more probable that certain distances between the end-points cause the algorithm to puke. Units don't really exist in the code, they are only used to format distances in the UI.

 

Can you post a file that fails to compute?

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

It doesn't like large numbers 1000+

Attached example files and screen shots. I have non-dimensionalized the value for the catenary length. You can see for the case when you change units to in and allow rhino to scale the model correctly from m, we get an incorrect faceted profile for the catenary. I have experienced this issue every time i have used the catenary component in imperial units.

 

 

Attachments:

I have a same problem, but mine catenary works when units is inches and units is mm I can only get lines

Hey David did the attached help illustrate the problem?

Yes it did. Giulio suggested a fix and it seems to work now on large distances.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service