an improve selfsufficiency of cities, minimum at areas with bigger dencity >
not sure for Manhattan or Hong Kong, I am thinking more in direction of re-designing smaller cities like Graz, Wien(Opernring) , Barcelona maybe (just to get out of Austria :)
Like pimp my city, or sustain my city :)
City Map>
I getting a dwg-s for cities from OpenSourceMap, Maperitive and Ghowl (Terrain) and importing them in to the Rhino.
GH>
Random extrusion for existing buildings, search for squares or other empty places and making a start circles there, moving in z-achse, offseting a litle bit (not logical just estetical purpose) and connecting group of 2 circles with Minimalsurface.
With Kangaroo build a Mesh above, then some Weavebird components and it is done.
Question>
I do not have algorithimic problem at a moment, more architectural!
1. I search for a cities with "nice" core, old parts (Innenstadt), suitable for intervention, like that they have old castle appearance, bigger dencity, smaller buildings height, river for water ect...
At moment I am working on Graz Innenstadt, and next is Wien Opernring///
2. Some ideas for art of meshing subdivision and Digital Fabrication?
3. Proposal for temperature study inside closed glass structure?
Any Green Idea, that can be implemented is also welcome!
Igor
…
ifically: I have a 100' vertical plane lofted between curved top and bottom profiles. I contour it every 8' (normal direction is Z, giving me 13 horizontal curves). I use Divide Curve to divide each contour into 10 segments. The "Points" output of Divide Curve now yields 13 branches with 11 items each, corresponding to 13 contours with 11 points from the left end of the curve to its right.
I now want to string "vertical" lines, and connect all the 2nd items in each branch together, all the 3rd items, etc... in order to make a polyline that travels between each 2nd point or 3rd point. i don't want to use Cull Pattern/Nth/Index because the number of subdivisions could change (11 could become 20, etc).
How do I connect the Nth item of each branch in this tree? Moreover, how do I connect all values in a branch with their corresponding values in all other branches?
Thanks for any replies,
Richman Neumann
Solomon Cordwell Buenz Architects
…
hange to a rectangle or a sequence of lines to get the tube geometry. Author of the video explained how to do this in the comments, but that didn't help. :(
"Alan Rodriguez Carrillo 1 year ago + Aldo Villanueva Hi, what you can do is try to handle points (4) with the ListITEM component and change the order of relation, for example (0,1) (1,2) (2,3) (3, 4) (4.0) in a panel. Subsequently do the relation of points through a line from points or LineSDL and elaborate the same steps that are explained in this video. Thanks.
Carlos González Puchol 11 months ago + Aldo Villanueva + Alan Rodríguez Carrillo Buenas, Alan and Aldo. I made a closed, tube design. First I listed the 4 points and put them in order with the polyline the polyline, making it closed. Then I had to close them also in the last steps before doing the triangulation."
Can anyone explain how to make this work ? It seems easy. For a person that knows the trick :))
https://www.dropbox.com/s/9dnyfoielum6m1r/PABELLON_last.3dm?dl=0 https://www.dropbox.com/s/y8xdiaf66xbyn9l/PAVILION.gh?dl=0…
tained from the Total Station etc survey.
Step 2: Use the Bake option in the PointXYZ menu to transfer the points to Rhino. This is how the point cloud looks after baking. These points have different elevations.
Step 3: Run the PATCH command in Rhino. It asks to select the points. The result obtained with default settings. Quite good representation of actual topography.
Step 3.1: Changing the value of parameters U and V in PATCH options to 20 each resulted in the next image.
AWESOME!!!!…
Dogs) i.e. the Holly Grail in Engineering/Design ... although rather easy is 100% impossible without code (especially when you need to manage "solution variations" (alternatives) and recall them any time) ... but I have a strong feeling that you wouldn't be able to handle this: expert only territory. Make a test: get a flat 2d grid of points (a Tree with a single dimension) and attempt to modify Z in points that you choose on a per point basis.
"Impossible" eh?
3. Without Mesh Machine areas like this:
would buy you a ticket to hell (one way).
All in all: doing this properly (The interactive part whilst checking valid typologies PLUS this, this and that) IS NOT a task for a novice by any means. I would strongly suggest ... er ... hmm ... the Soap Opera approach (but this also requires code if a non rectangular grid is used as a "mesh template").…
Vertices.Count * 3]; int[] facesizes = new int[m.Ngons.Count]; List<int> faces = new List<int>();
int j = 0; for (int i = 0; i < m.Vertices.Count; ++i) { verts[j] = m.Vertices[i].X; ++j; verts[j] = m.Vertices[i].Y; ++j; verts[j] = m.Vertices[i].Z; ++j; } for (int i = 0; i < m.Ngons.Count; ++i) { MeshNgon mngon = m.Ngons.GetNgon(i); facesizes[i] = mngon.BoundaryVertexCount; for (int j = 0; j < mngon.BoundaryVertexCount; ++j) { faces.Add(mngon[j]); } }
CarveSharp.CarveMesh cm = new CarveSharp.CarveMesh(); cm.Vertices = verts; cm.FaceIndices = faces.ToArray(); cm.FaceSizes = facesizes;
return cm; }
Going the other way should be similar, though I don't know if you need to define Mesh faces and then N-gons, or if you can just define N-gons right away and it'll take care of the Faces list for you... Haven't tried the Rhino 6 API... Not sure if you can just use the index operator on MeshNgon directly or you have to go mngon.Item[i] or whatever.
And then instead of
Rhino.Geometry.Mesh res = CarveRC.CarveOps.PerformCSG(...)
do
CarveSharp.CarveMesh res = CarveSharp.PerformCSG(CarveMeshA, CarveMeshB, CarveSharp.CSGOperations.Union);
Mesh m = res.ToRhinoMesh();
or your own CarveMesh-to-RhinoMesh function which preserves N-gons.
…
Added by Tom Svilans at 8:45am on September 25, 2017
rring to the above image)
Area
effective
effective
Second
Elastic
Elastic
Plastic
Radius
Second
Elastic
Plastic
Radius
of
Vy shear
Vz shear
Moment
Modulus
Modulus
Modulus
of
Moment
Modulus
Modulus
of
Section
Area
Area
of Area
upper
lower
Gyration
of Area
Gyration
(strong axis)
(strong axis)
(strong axis)
(strong axis)
(strong axis)
(weak axis)
(weak axis)
(weak axis)
(weak axis)
A
Ay
Az
Iy
Wy
Wy
Wply
i_y
Iz
Wz
Wplz
i_z
cm2
cm2
cm2
cm4
cm3
cm3
cm3
cm
cm4
cm3
cm3
cm
I have a very similar table which I could import to the Karamba table. But I have i_v or i_u values as well as radius of inertia for instance.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
dimensjon
Masse
Areal
akse
Ix
Wpx
ix
akse
Iy
Wpy
iy
akse
Iv
Wpv
iv
Width
Thickness
Radius R
[kg/m]
[mm2]
[mm4]
[mm3]
[mm]
[mm4]
[mm3]
[mm]
[mm4]
[mm3]
[mm]
[mm]
[mm]
[mm]
L 20x3
0.89
113
x-x
4,000
290
5.9
y-y
4,000
290
5.9
v-v
1,700
200
3.9
20
3
4
L 20x4
1.15
146
x-x
5,000
360
5.8
y-y
5,000
360
5.8
v-v
2,200
240
3.8
20
4
4
L 25x3
1.12
143
x-x
8,200
460
7.6
y-y
8,200
460
7.6
v-v
3,400
330
4.9
25
3
4
L 25x4
1.46
186
x-x
10,300
590
7.4
y-y
10,300
590
7.4
v-v
4,300
400
4.8
25
4
4
L 30x3
1.37
175
x-x
14,600
680
9.1
y-y
14,600
680
9.1
v-v
6,100
510
5.9
30
3
5
L 30x4
1.79
228
x-x
18,400
870
9.0
y-y
18,400
870
9.0
v-v
7,700
620
5.8
30
4
5
L 36x3
1.66
211
x-x
25,800
990
11.1
y-y
25,800
990
11.1
v-v
10,700
760
7.1
36
3
5
L 36x4
2.16
276
x-x
32,900
1,280
10.9
y-y
32,900
1,280
10.9
v-v
13,700
930
7.0
36
4
5
L 36x5
2.65
338
x-x
39,500
1,560
10.8
y-y
39,500
1,560
10.8
v-v
16,500
1,090
7.0
36
5
5
I have diagonals (bracings) which can buckle in these "non-regular" directions too, and they do. If I could add those values then in the Karamba model I could assign specific buckling scenarios..... I can see another challenge which will be at the ModifyElement component, I will not be able to choose these buckling lengths, in these directions.
Do you think this functionality can be added within short, or should I try to find another way to model these members?
Br, Balazs
…
"meshed" i assume that meant converting Surfaces with MeshUV\DeMesh?, and from your screenshots thats a substantial number of vertices and therefore lines to draw, well worth it though from the results!, i agree with your answer to 3) that a more automatic solution is required,.
1) By mesh, I should have said produce a surface – then convert surface to mesh – followed by de-mesh to get access to vertices etc.
You can reduce the resolution of points if you need to, depending on your hardware. The more points you use the harder and it is to compute a solution, however the more points you use, the more accurate your interpolated surface. You need to find your own balance between speed and accuracy.
- ..thats great news, equalizing vertex numbers is exactly what i need to do since my Blend surface "keyframes" by nature will likely have unequal point counts. However, a) ..when using default Rhino surf's your intruiging def. starting to work for me only after i replaced you "custom" Domain(VB\Python?,let me know) with Deconstruct Domain. then it connected each surf's vertices but did Not produce an intermediate surface or points. b) ..when using my IDENTICAL Blend surf's in your def. with Deconstruct Domain and Merge comp's it then produced intermediate vertices,. see def. screenshots or i can send def's i you like,. I'll also produce the 2nd, Non-identical Blend surf keyframe to test in your def.
2) I am not sure what you mean by my ‘custom domain’ are you referring to the definition in my second post – or the post I sent for David to look at? Perhaps you can circle the component and upload a screenshot so I know what you are referring to? Your second screen shot appears to have worked OK
- .. agreed, 6) does or will your latest def. contain more automated, vertex correspondence, Ln creation?
3) No, I moved away from morphing surfaces and moved my solution to generating surfaces based on point data. This cut out the requirement for me to generate the surface to begin with and allows very automatic production of surfaces from data out of excel. Perhaps this would also be a good solution for you? You could:
Move your point data to excel, by exporting the x, y, z of your vertices for each surface.
Use excel as your information repository then write a definition to interpolate between your start and end points from excel.
This is basically what I have done now, as I have 1700 different ‘surface’ snap shots from the data I am working with.
- ..perhaps i missed something, but after using Brep > Join on my polysurface SDivide still saw it as subsurfaces instead of a single surface,.
4) Sorry, perhaps I should have tried that – I didn’t get as far as trying to subdivide. There should be a way to then re-create as one surface if it is necessary… I will try and find out when I have time.
How many sets of surfaces are you trying to merge through? It is also possible to morph from 1 to 2, 2 to 3, 3 to 4 …… x-1 to x by using a slider which calculates the range and picks the correct two surfaces to morph. If you need more info let me know and I will write something. - ..that sounds perfect, esp. since the sets of surfaces will be as nearly unlimited as the feature film they're modeled from. Yes, i'd love to learn more info\def's on this subject, thanks,..
Sounds to me like you might be better taking the excel read, interpolate route? If you have nearly unlimited surfaces, then they must be generated from some other data source yes?
Let me know your thoughts, if you would like to discuss anything I am happy to make myself available on skype at some stage to talk you through some of this stuff.
Cheers
Lyndon
EDIT: I have uploaded a video, which shows a surface generated using excel data - which basically loops between 'snapshots in time' to give you an idea of whether this would suit your needs.
https://www.youtube.com/watch?v=f9XAne9byQc&feature=youtu.be
…
orged a meter component in place to get to read the data.
GH Python lists me spring 3 xy and z format [x1, x2, x3,...] [y1, y2, y3,...] and [z1, z2, z3,...]
The VB code is simple: (A = CDbl (x))…
Added by Rémy Maurcot at 2:39am on October 14, 2011