Grasshopper

algorithmic modeling for Rhino

A smarter way of doing this - Crash detection

Hi there,

I'm getting close to finalizing my node definition.

One of the last steps is to optimize the position of each node so that they are as close in to the center point as possible. This in order minimize printing cost and avoid mesh issues when they collide.

I've made an initial definition which does want I want but is not accurate nor recursive, it simply moves forward once by a given value if it collides.

Is there a more accurate way of doing this? Ideally setting a distance between each rod and working out the placement according to this, perhaps using a solver?

Thanks in advance,

Charles

Views: 5301

Attachments:

Replies to This Discussion

Permalink Reply by peter fotiadis on April 24, 2015 at 11:44am

Hmm ... this is challenging (your cases).

There's some wrong structure (hard to say what exactly) but:

1. Use this in order to visualize what SandBox did:

2. Then examine the "central" node on your chair (missing connectivity data therefor C# can't compute accurately the clash stuff and defaults to some "safe" mode, more upon that soon):

3. Compare with my chair (but then again this is made with the pro AEC C# version and is 100% faultless):

Moral: we need extensive topology "cross" checks VS the stuff that SandBox does (the connectivity DataTrees, that is).

RSS

About

Scott Davidson created this Ning Network.

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service