Rhino/Grasshopper Crashing With Topo Lines

Having an issue working on the progress update, as it keeps crashing after doing almost anything with the topo lines at this point (connecting/disconnecting/baking). I'm not sure what's slowing it down so much, and I am not loading it from a usb. Please let me know if there is anything I can do! I will attach the files as well. Some things on the definition are disconnected at the moment because I can't save it working.

Attachments:

Midterm-Process-Thall.gh, 46 KB
topo2_roden.3dm, 4.5 MB

Replies to This Discussion

Permalink Reply by Rajaa Issa on February 5, 2015 at 7:41pm

Try to turn on the "Profiler" (found under Display>Canvas widgets) to see where you are getting stuck.

Permalink Reply by Michael Riggin on February 6, 2015 at 3:07pm

Olivia, I noticed a couple of things wrong, including what I think is causing the crash.

- You have a topo layer that's at 0, so your first Division component is returning a divide by zero error. Shifting all the layers up by the same value ( 0 becomes 1, 10 becomes 11, etc) will fix this.

- You are connecting the last curve parameter of the first step to the first curve parameter of the second step. Instead, bake the first curve parameter, then assign the baked curves to the second curve parameter. That way you can later directly manipulate the scaled curves.

- Finally, you never scaled the topo to the model size, 12" x 12", so you are asking the Curve Division component to divide each curve that is thousands of feet long by segments that are a fraction of a foot. It's doing it, but that task would take so long that it appears to be 'crashing' from your perspective.

I tested these fixes and it runs fine, although I have noticed that you scaled model is running beyond the domain for Z-values. I believe it's a weakness of the example definition. The definition I posted makes use of a Remap Numbers component instead of using division/ratios. This should fix that problem. Thanks for posting!

Attachments: