Kangaroo Springs Runtime error

hello!

i've been stumped for a few hours and thought i would see if the crowd here could help out.

i am trying to get a minimal surface from the boxy mesh i modeled in rhino however, after extracting the wire edges with the weaverbird component and plugging these lines into the kangaroo spring component, i get the runtime error that a spring cannot have a zero start length. any ideas on why this is happening?

i tested the same definition on a smaller mesh object and it worked fine. perhaps it is my mesh?

i am attaching a simplified version to show where the error happens.

any help would be appreciated!

Attachments:

Replies to This Discussion

Permalink Reply by Yoann Mescam (Systemiq) on January 23, 2012 at 2:09pm

There are 221 curves with lengths under 0.0005 and the Spring component just considers these as zero length curves.

Lower the tolerance or cull these curves.

Permalink Reply by carrie mcknelly on January 23, 2012 at 4:04pm

thank you! that did the trick.

now let's see if i can make it do what i want from here!

Permalink Reply by Alex Webb on July 2, 2012 at 2:43pm

I tried this on a similar problem, but I'm not getting an invalid mesh output. if I'm selectively choosing the springs instead of all of the lines that comprise the wireframe, won't that make an invalid mesh every time?

how can I lower the tolerance on the spring component?

Permalink Reply by dzeba on August 15, 2012 at 7:45pm

Hey - Im facing the same problems !! anybody here who can help ??? thanks

Permalink Reply by Ankit Savla on March 12, 2015 at 1:30am

I have the same problem, but can you also tell me how to Lower the tolerance or cull these curves.

Permalink Reply by John Zhune on February 14, 2019 at 10:30am

same problem hexagonal%20cells.gh my%20model%20for%20the%20ferry%20terminal.3dm

Permalink Reply by John Zhune on February 14, 2019 at 10:30am

hexagonal%20cells.gh

Permalink Reply by Thomas Yulki Takeuchi on February 14, 2019 at 4:11pm

I'm not sure if I understood your problem correctly, but I'm pretty sure that Cull Index component is not being used right. You should input an integer, not a string.
If you are trying to cull overlapping lines, use only the remove Dup Lines from lunchbox.hexagonal%20cells.gh

Good luck!

Permalink Reply by John Zhune on February 19, 2019 at 2:32pm

thanks thomas, this is interesting. I'm learning as I go. Okay now I get the difference between Integer and String. However I don't get how each can be used in this example. Is there a way to access the code of the design to see how it's affecting it? :) I've tried to re-open these files to fix the design a bit and now it's telling me something else. I have new questions now lol

RSS