the geometries in a component ("set multiple 'geometries'"). If you have 100 curves and would like to add(/remove) 1, you need to select 101(/99) curves in Rhino, it could be annoying.
2) you use the "manage 'geometry' collection" with the Object ID but I don't like this way.
3) you create a new component with the new geometries and you merge the two components.
My point is that it would be useful to add/remove geometries like you set them by picking them up in Rhino, the current collection being selected automatically.…
a close collaboration with them. Keep in mind that a membrane is 1% the "tissue" and 99% the nuts and bits that keep the tissue properly in place. In order to design bespoke nuts and bits you'll need a decent feature driven solid MCAD app (from CATIA/NX to Solidworks) - Rhino is NOT suitable for that type of work by any means.
The Catch 22 is that these specialized fellas they don't pay any attention to you if they don't know you ... but in order to know you ... blah, blah. …
omponents - more on that soon. By that I mean that the focus of the design (even on Academic level) should concern totally different things than the fabric.
So ... leaving aside the components (for the moment) let's examine the simplest (cone free) design: get a polyline and do something using the classic one node up, the next down approach.
Using the 099 K1 engine (behaves better in some occasions, not in this particular case ... but anyway).
Using Starling/WB as well.
more soon.…
the mesh and 2 curves which represent the problem vector intersections. The VB script:
Dim cell_tot As New List(Of Integer) Dim ray_int As New list(Of line) For i As Integer = 0 To cells.Count - 1 Dim intx As Integer = 0 For j As Integer = 0 To pts.Count - 1 For k As Integer = 0 To sample_V.Count - 1 Dim r As Ray3d = (New Ray3d(pts(j), sample_V(k))) Dim cell_intx As Double = Rhino.Geometry.Intersect.Intersection.MeshRay(cells(i), r) If cell_intx > 0 Then intx = intx + 1 Dim l As New line(pts(j), sample_V(k), 100) ray_int.add(l) End If Next Next cell_tot.Add(intx) Next A = cell_tot B = ray_int
This works with 99% of the vectors but seems to systematically miss some. Wondering if it is a tolerance issue or if I am messing up the code. Screenshot of the geometry, rhino model, and GH defn attached.
Thanks,
Jeff…
oking for a project Architect meaning an individual who knows top to bottom the whole route:
1. 1% is the conceptual/"sketch" design phase be that smart or traditional (in fact is less than that since everybody does "wild" things the one way of the other these days: finally it doesn't make any difference, just another twisted thing among other twisted things)
2. 99% is the shop drawings + specs + quantifications + tech descriptions.
3. 1345% is the ability to deliver something that is not laughable (and avoid the design construct alternative, the end of days that is).
BTW: making a Boeing 777 (the very first thing made without "papers" around) isn't convincing enough for mastering "work flows"?
…
ata in Grasshopper. So we learned a lot about data sources, environmental data, etc. and how to use them in GH. It was a great experience and was my start with GH. I knew it a little bit, but I learned so many things about it there. Not sure if they will do it again, but it was quite successful, so maybe they will.
I have not used ELK before, so can't comment on it, but I can confirm that it took a really long time. But for the most part even for a very large architectural project you wont need OSM data for a whole city, especially not one as big as Paris. So if you want to use ELK use it with normal size maps like a few hundred meters square, because 99% of projects wont be bigger than that. If they are then you will have the proper resources ;)…
Added by Armin Seltz at 8:16am on November 6, 2015