algorithmic modeling for Rhino
Hello,
First of all, as this is my first post (although it's not the first time I find useful info here), I'd like to thank everybody in this community for all the passion and time you put in this forum. So, thank you :)
Now, let's get straight to the point. I study Architecture and I'm working on a project with a bone-like structure, based on a fabric-cast concrete method developed at the University of Arizona.
http://www.dezeen.com/2016/05/19/ron-culver-joseph-sarafian-fabric-...
By now, I have worked out how to design the joints and connections of my structure which will be of course significantly different, so I I'm fairly sure that the project is consistent and matches the course requierements.
However, I've found trouble building a general model of the structure in Rhino 3D. I've built a wireframe model, placing each and every strut exactly (well... maybe it's not that accurate xD) were it has to be... so, now I have a nice wireframe composed of line segments connecting points. I have to turn it into a a so-called "skeletal mesh" (this is the best known name for it in the forum, isnt't it?). I've heard of some tools such as the Exoskeleton plug-in, but I'd like some advice on the best way to make a skeletal mesh out of line segments.
I would also like to take a further step in the modelling of the structure, which may be too ambitious... please let me know your opinion about it. I know of some GH plug-ins that provide structural analysis, such as Karamba. Could I somehow link the results of the structural analysis to the skeletal mesh algorithm (exoskeleton or whatever), so the stress level of each bar determines its thickness?
To conclude, I would like to say that I know that this task far exceeds my curent knowledge of parametrig design (I'm quite proficient with Rhino, but a noob with GH). A classmate with further knowledge about it will be helping me, but I would really like to have some idea about what should be done. Of course, I don't expect any detailed tailored tutorial from you, as I don't want to abuse your kindness. I'd just like some general advice.
Thank you very much,
Carlos
Tags:
Yikes (+ Yikes)
This is "simple" (for surfaces) and rather totally unsuitable (for a novice) when thickened stuff (joins et all) are invited to the party.
Let's start from the simple case:
1. You have a line graph actually: nodes (points) that are connected (or not) with others.
2. All that you need is a concept called connectivity tree (but you MUST know what a DataTree is). Get Sandbox add-on ... feed the lines List and have the what-is-connected-to-what on hand: points to points, points to lines, lines to lines.
Spam on:
Given a ListA and ListB a AtoB connectivity tree is some ominous thingy (a DataTree of int type) that has branches with main dimensions the indices of ListA and contains indices related with ListB. Freaky stuff eh?
Spam off.
3. After "sampling" the related "loop" lines (so to speak) create edge surfaces out of these.
After that ... comes the pain (and the tears) ... since thicken all that stuff and having real-life water tight "joints" in mind ... well ... this is not very simple (but viewed from an Academic perspective is piece of cake).
So do the easy thing and post your results for the tears part, he he.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2025 Created by Scott Davidson.
Powered by