Grasshopper

algorithmic modeling for Rhino

3D voronoi skeleton definition not working on final output

Hey, I was introduced to GH about a week ago, wondering if anyone can help me out.

It's someone else's definition but my own doesn't get the results I require.

The mesh attached isn't the final I wish to apply the definition to, but it allows me to understand if it will be of any success.

The file attached under " test" are my efforts in trying to achieve my desired output. However, the bases of that uses a box and not a mesh. So I scoured the forum here to discover someones definition that achieves it with a mesh.

However, only half of the definition works, I cannot get the final output 

Many thanks in advance.

Views: 3884

Attachments:

Replies to This Discussion

I'd really appreciate any assistance

I'd really appreciate some help with this, I am eager to learn this program. So if anyone could offer some advice on how I could resolve the above definition to workout i'd be forever grateful 

Is this is what you are after? If yes (get Exo W, Exo 1, Topologizer) , I'll upload the def for you.

Yes it is!

You'll have to excuse me, Exo w, exo 1, topologizer? are these plugins?

I really appreciate your help!

Well...

1. Yes these things are plugins and the main job here is done by the Exoskeleton (but the bad news are that IMHO the new Exoskeleton - called Exo W - is highly temperamental)

2. Anyway if Exo W is not working, try the old Exo (001) as well.

best, Peter

Attachments:

Thank you very much for what you've done, the result is actually exactly my desire.

However would it be possible to make it work withing a mesh I created, instead of being within domains set by grasshopper?

Thank you once again

Well... in fact I did nothing (new I mean). What I did some time ago is to "sample" some ways to get "wires" and do something (using Cyto, Exo and Topo: GH plug ins developed by some very bright minds).

Other than a myriad posts related with the above fascinating plug-ins (search the Forum), have a look on this:

http://www.grasshopper3d.com/forum/topics/cytoskeleton-vs-exoskelet...

For using these 3 in response to some "similar" user request (a bit complicated, mind especially with mesh simplification issues) see this: http://www.grasshopper3d.com/forum/topics/solid-model-to-voronoi

See this as well: http://www.grasshopper3d.com/forum/topics/radius-change-by-attracto...

And this: http://www.grasshopper3d.com/forum/topics/3d-voronoi-substraction-w...

Finally for "simplifying" meshes is worth giving MeshLab (free) a spin.

Here's the (traditional, he he) update for you: Added a Brep (from TSpline) and the same thing converted to Mesh ... and then converted to brep in order to allow "apples-to-apples" type of ops with the Voronoi breps.

Load Rhino file first since the 2 are NOT internalized (Box is "stand-alone" anyway). Notice a myriad of conditions that make Exo W red (and some very odd results if you play with values). That's partially expected because a Voronoi brep may yield "tiny" edges that could yield non manifold "tubes" ... but still there's cases that in theory could not cause Exo W any trouble.

See the ex mesh VS the donor brep:

Attachments:

PS: In general I would say that these plug-ins they certainly work ... but NOT for any value combo imaginable: for instance as delivered above the box option: all plus the Re,Rs values chosen ... they yield a red Exo W (apparently some non manifold situation). Change values to something like this in order to get the desired result:

Added a 3rd option.

Attachments:

You are truly helpful! I cannot thank you enough.

Having a play around with these, trying to get my mesh and make them work! 

Is it my model which is impossible to work with? or is it myself not seeing the obvious.

Attachments:

As regards the meshdesk1 mess ... I mean mesh, he he:

Your goal is to design some abstract form AND then "drill" that thing and create an orgy of "fused" tubes, right? 

Well ... if this is the case I would strongly suggest to give TSplines a spin (the only subdivision modeling approach that I like, he he) that could yield a nice brep (polysurface) when back in Rhino. Then we could ("easily") chop/voronize the big thing into a paranoid spaghetti of "fused" tubes and put the glass on top.

WARNING: NOT all geometries and all parameter values yield a solution ... because we are talking about quite complex things that MAY result non manifold nodes/tubes.

Attachments:

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service