algorithmic modeling for Rhino
There are a couple of things about your definition...first of all, Kangaroo has a great utility in it that creates connectivity between all points in a set...you have a fair amount of duplication in your inter-connectivity network that this cleans up really quickly. Secondly, you may want (in addition to your springs with cutoffs) to employ a power law to help pull all of the circles together, rather than the unary forces you are employing here. Basically you're just pushing them upward in space...but a power law actually engages in attraction between them. So your elements actually pull toward each other in general, and then your springs keep them apart in close proximity. So I would use the power law force to pull them together, and then relax it once you've achieved a suitable organization.
I have tried using this power law recently and could not make it work - it results in an index error. So I decided to have a look at examples here and have a couple of questions. First of all, here it gives me the same index error. (I can see the force input is flattened - nevertheless.) Secondly - why is the spring component different from the one I have - it has (cutoff, compfail, tensfail)
It might be basic, but due to insufficient knowledge I require some clarrification please.
Much appreciated.
Hello Anton,
I changed the spring component a bit between versions 0.06 and 0.074, but I left the old one in as a legacy component (so definitions using the older spring component will still work). That's why you see these differences.
Do you still get the index error when switching the SimulationReset toggle to true ?
All right - it works :) thank you for help
YESSS
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by