Hey Visose, The truss system looks pretty interesting. I hadn't realized that the function that I had asked about earlier was only helping solve the intersections to get the final curve output. Since we had set up our systems a little differently, I didn't need to use that function, because I already had the reference planes centered on the rib from the beginning of the definition. Anyway, I finally finished the system and posted the source file on my website if you would like to take a look. Here's a link: http://www.liftarchitects.com/journal/2008/10/27/waffle-structural-system-using-grasshopper-to-output-structu.html Keep up the good work, and I appreciate your help along the way. Best, Andy
On Oct 25, 3:45 am, visose <[EMAIL PROTECTED]> wrote: > I would actually ignore that function, it's a very poor way of > centering them since the origin of the points are placed slightly > diagonally. This affects the placing of the sections in the xy plane. > A better way would be something like getting the z vector of the > plane, multiply it by x/2 and add it (point+point) to the origin, so > the planes stay parallel to the axis. > > The definition can be also modified to create > trusses:http://grasshopper3d.googlegroups.com/web/trusses.jpg > Thought its a bit buggy right now (i had to delete manually some > pipes). > > On Oct 25, 1:33 am, visose <[EMAIL PROTECTED]> wrote: > > > Sure, function component has the following expression: {x/2,-x/2,0} > > where x is the width of the beam, but this is used only to center the > > section-planes on the beams. I don't think there is any other hidden > > variable or formula in any other component of the screenshot. To > > orient them i just used the orient by plane component. In the input > > geometry the section curves, in the reference plane its corresponding > > cut-plane and in the target plane a XY plane but changing the point of > > origin so they are not placed on top of each other. > > > About my definition being a square grid, you can have a different > > spacing in each axis by just merging an additional slider and no other > > changes:http://grasshopper3d.googlegroups.com/web/woodframexydifsp.jpg > > You can have all the x and y values in the same lists even without a > > square grid and use a split list when required, this way you can avoid > > duplicating a lot of components. I admit i find it a bit counter > > intuitive, but afaik all this is being rewritten and we will be able > > to have lists inside lists (i think). > > > On Oct 24, 11:13 pm, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > Visose, > > > Could you explain a little more about how you were able to orient your > > > curves on the XY plane? I have the basic idea, but it looks like your > > > using a single variable function in your definition. I was just > > > curious as to what expression you were using in that function? > > > Thanks, > > > Andy > > > > On Oct 24, 1:51 pm, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > > Visose, > > > > I spoke too soon... I hadn't read your last post about orienting the > > > > curves on the ground plane. Very nice. I had thought about doing > > > > that too, but you beat me to it. I'll try to add those components > > > > into my last definition. Thanks again for your help. > > > > -Andy > > > > > On Oct 24, 1:45 pm, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > > > Thanks viosose, > > > > > I liked the way you developed your system, but there were a couple of > > > > > things that were different between our systems. Your's works on a > > > > > completely square grid system using an interval to calculate the > > > > > dimension of the grid. I wanted the user to be able to just dictate > > > > > the number of division instead of a specific distance allowing them to > > > > > use a non-uniform grid pattern (although the two methods are basically > > > > > interchangable). But I did really like how you solved the notching > > > > > problem, so I re-wrote my definition to use a similar method and it > > > > > worked great. I ultimately wanted a single curve and not the solid > > > > > extrusion so that the curves could be output to a lasercutter, so I > > > > > added a few steps to get the final curve result. I also added a label > > > > > function so that you could keep the number of struts organized. I > > > > > think this definition is now done, and I'll post the final version on > > > > > my websitehttp://www.liftarchitects.com. I've also posted 2 > > > > > screenshots of the definition and the grasshopper definition here: > > > > > Source Files: > > > > > Screen Shot > > > > > 1:http://grasshopper3d.googlegroups.com/web/waffle+system_full+shot.jpg... > > > > > Screen > > > > > Shot2:http://grasshopper3d.googlegroups.com/web/waffle+system_detail.jpg?hl... > > > > > Grasshopper > > > > > Definition:http://grasshopper3d.googlegroups.com/web/waffle+system_10.ghx?hl=en&;... > > > > > Thanks for your help. > > > > > Best, > > > > > Andy > > > > > > On Oct 24, 12:35 pm, visose <[EMAIL PROTECTED]> wrote: > > > > > > > Since you mentioned it's for laser cutting, I added some components > > > > > > that place the beam outlines neatly in the ground > > > > > > plane:http://grasshopper3d.googlegroups.com/web/projectbeams(2).jpg > > > > > > Btw, ignore the previous comment. The slope happens perpendicular to > > > > > > the outline of the beams. Since the objective is to achieve only the > > > > > > outline of the beams, this is not a problem. > > > > > > > On Oct 24, 8:25 pm, visose <[EMAIL PROTECTED]> wrote: > > > > > > > > Btw, i don't think the method i used to create the notches is the > > > > > > > most > > > > > > > appropriate since bottom of the opening will have the same slope > > > > > > > as > > > > > > > the top of the crossing beam so they won't fit tightly. > > > > > > > > On Oct 24, 7:50 pm, visose <[EMAIL PROTECTED]> wrote: > > > > > > > > > It's true, the boolean difference doesn't work with extruded > > > > > > > > surfaces. > > > > > > > > I created a boolean difference script with the VB.NET component > > > > > > > > and > > > > > > > > also doesn't work, so the problem may be either from the boolean > > > > > > > > difference sdk (which i doubt) or from the extruded surface > > > > > > > > component. > > > > > > > > I couldn't find an example of how to script a extruded surface > > > > > > > > in the > > > > > > > > wiki. > > > > > > > > > Nevertheless, I recreated a definition of what I think you are > > > > > > > > trying > > > > > > > > to achieve without extruding a surface. Maybe It will help > > > > > > > > you.http://grasshopper3d.googlegroups.com/web/woodframe.jpghttp://grassho... > > > > > > > > > On Oct 24, 4:54 pm, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Thanks. I'm still unsure why the boolean difference isn't > > > > > > > > > working on > > > > > > > > > this file. I made a separate file where I had a cube and a > > > > > > > > > shpere as > > > > > > > > > two Breps... and then I used the Boolean Difference to "trim" > > > > > > > > > out one > > > > > > > > > from the other, and it works like you think it would. Only, > > > > > > > > > when I > > > > > > > > > try that in this file, it doesn't seem to work. I've been > > > > > > > > > extruding a > > > > > > > > > planar surface to give me a closed Brep. Both the Notches > > > > > > > > > and the > > > > > > > > > extruded struts show that they are closed Breps, and yet when > > > > > > > > > I use > > > > > > > > > the Boolean Difference component, all that I get is a empty > > > > > > > > > Brep set > > > > > > > > > as a result. Any ideas? > > > > > > > > > Thanks, > > > > > > > > > Andy > > > > > > > > > > On Oct 24, 12:36 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > Hi Andy, > > > > > > > > > > > trimming is always a bit more tricky, if only because it's > > > > > > > > > > not clear > > > > > > > > > > which remaining parts you want to keep. If you're trimming > > > > > > > > > > a single > > > > > > > > > > surface with a closed loop, it's not ambiguous, but > > > > > > > > > > otherwise... > > > > > > > > > > > I'll look into adding a bunch of trimming components, for I > > > > > > > > > > doubt that > > > > > > > > > > one will do the trick. > > > > > > > > > > > -- > > > > > > > > > > David Rutten > > > > > > > > > > Robert McNeel & Associates > > > > > > > > > > > On Oct 24, 1:23 am, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > David, > > > > > > > > > > > I see that there is an "Untrim" surface component in the > > > > > > > > > > > last install, > > > > > > > > > > > but is there a trim command that I could use in this > > > > > > > > > > > case? Would it > > > > > > > > > > > be something that will be released in the new version? > > > > > > > > > > > Or should I > > > > > > > > > > > try to make some sort of work around? > > > > > > > > > > > Thanks, > > > > > > > > > > > Andy > > > > > > > > > > > > On Oct 23, 1:18 pm, Rchitekt <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > I've been working on a waffle system that creates an > > > > > > > > > > > > "egg crate" > > > > > > > > > > > > structure from any set surface in Rhino. It has > > > > > > > > > > > > parametric sliders to > > > > > > > > > > > > control how far you want to extrude the surface, the > > > > > > > > > > > > number of > > > > > > > > > > > > divisions in the x and y axis and the material > > > > > > > > > > > > thickness of the actual > > > > > > > > > > > > struts. Ideally, this definition would be used to > > > > > > > > > > > > create laser cut > > > > > > > > > > > > models of any surface, and the notches would be already > > > > > > > > > > > > put into each > > > > > > > > > > > > strut. I'm having one small problem. I've generated > > > > > > > > > > > > the boundary > > > > > > > > > > > > curves (the strut outline) and I've been able to create > > > > > > > > > > > > the notches > > > > > > > > > > > > based on the material thickness. My problem is I can't > > > > > > > > > > > > seem to join > > > > > > > > > > > > the two... meaning, I can't seem to trim out the notch > > > > > > > > > > > > portion of the > > > > > > > > > > > > boundary curve and get one unified curve that could be > > > > > > > > > > > > immediately > > > > > > > > > > > > sent to the laser cutter. I've tried to create solids > > > > > > > > > > > > out of the > > > > > > > > > > > > struts and the notches and doing a boolean difference, > > > > > > > > > > > > but it didn't > > > > > > > > > > > > seem to give me any kind of usable output. I'm very > > > > > > > > > > > > close to > > > > > > > > > > > > finishing this script and I'm just curious if anyone > > > > > > > > > > > > could help me on > > > > > > > > > > > > this last step. Here's a link to the screenshot of how > > > > > > > > > > > > the script > > > > > > > > > > > > workshttp://grasshopper3d.googlegroups.com/web/waffle%20system_01.jpg?hl=en > > > > > > > > > > > > And here is a link to the > > > > > > > > > > > > definition.http://groups.google.com/group/grasshopper3d/web/waffle%20system_08.g... > > > > > > > > > > > > Thanks for your help in advance. > > > > > > > > > > > > Best, > > > > > > > > > > > > Andy
