putational Planning Group (CPlan) and is a result of long term collaboration between academic institutions and praxis partners across the globe with the common goal to increase the efficiency and quality of architecture and urban planning.
For additional information, updates, examples and tutorials please visit DeCodingSpaces-Toolbox.org
Authors
Abdulmalik Abdulmawla1,
Martin Bielik1,6,
Peter Buš2,
Chang Mei-Chih2,
Ekaterina Fuchkina1,
Yufan Miao4,
Katja Knecht4,
Reinhard König1,4,5,
Sven Schneider1,3,6
Partners
Member institutions of the Computational Planning Group (CPlan):
1Bauhaus-University Weimar (Chair Computer Science in Architecture, Chair Computational Architecture)
2ETH Zürich (Chair Information Architecture)
3Emerging City Lab - Addis Ababa
4Future Cities Lab Singapore
5Austrian Institute of Technology Vienna 6DecodingSpaces GbR
Gallery
…
Added by Martin Bielik at 10:13am on September 28, 2017
4 explode the text
5 select the exploded text, which are now curves, and the border from step 2 and use the planarsrf command again
6 make your surface using the two curves at top and bottom and a section. Use the sweep2 command
7 select your negative text surfaces and use the flowalongsrf command
maybe the scale of the text can be edited by the size of the surface or of the text but I bet you can figure that out! good luck!…
t ''Morph'' turns Red saying ''Cannot morph from a degenerate box'' (image 2),
that's because every curve generates a box (image 3).
After what i check the Option ''Union'' box to make only one box for all the curves (image 4).
However, the result is aleatory and not accurate at all ... :/ (see image 6).I know you are developing Pufferfish and not ''Morph'' component, but recently you publish on instagram a video where i believe you could morph and Twist with success a collection of curves (please see image 7 and 8)...If you could give me a hint how that can be achieved, it would be awesome.(Piping/Meshing the curves with very small diameter will perhaps work and help for visualisation purposes, but i actually just need morphing Raw curves for fabrication purposes).Hope to read you very soon...Ghali,…
e actual method.
Below, I descibe how they work:
1) drag "scheduleDay" onto the canvas
2) drag some Gene Pool lists onto the canvas and connect a number slider - from 0 to 3.
3) connect the Gene Pool list to _genePool input. The component change some important features of the Gene Pool list automatically. Now you have LB_GenePool!!
4) choose the template that it's suitable for you.
5) disconnect LB_GenePool and if templates are not good, you can change them manually
6) drag "Ladybug annual schedule" onto the canvas
7) Connect LB_GenePools to inputs for the days of the week, Epw file and if you want to "_holiday" (in this way you consider holidays). Now you have your simple schedule.
8) a small workflow to visualize it into Rhino..
9) Connect "Ladybug annual schedule" to "Honeybee_Create CSV Schedule" to make your csv Schedule
You could make a schedule more complex than the one in the example above.
You can do that with _analysisPeriod input.
Bests
Antonello…
ers of the last surface in the Brep, however, only the corners of the bounding box of the surface are generated)
It seems the rs.SurfacePoints only returens the control points of a surface rather than the actual corners of the surface. Can you advise if there's a way to do it?
Thank you!
Code:
import rhinoscriptsyntax as rsall_parts = rs.ExplodePolysurfaces(brep)centers = []vectors = []lines = []vertices = []cnt = 0for part in all_parts: center, err = rs.SurfaceAreaCentroid(part) centers.append(center) #rs.AddText(str(cnt), center) uv = rs.SurfaceClosestPoint(part, center) vector = rs.SurfaceNormal(part, uv) vectors.append(vector) N_start = center N_end = rs.VectorAdd(center, vector) line = rs.AddLine(N_start, N_end) lines.append(line) #vertices = rs.SurfacePoints(part) vertices = rs.SurfaceEditPoints(part) cnt +=1#C = centers#N = vectors#L = linesV = vertices#todo:#explore the surface methods in rhinoscript.surface...#import rhinoscript.surface.…
Added by Grasshope at 10:34pm on September 15, 2015
cture (EPA_s)
When Karamba cross section optimiser is finding the most weight-efficient section for the given load then the actual EPA_s is just been calculated. The issue here is that one of the main load on a lattice tower is from the wind pressure. So the wind load is based on the EPA_s which we can get only after optimising the sections. With other words, one of our input is based on an output from the design.
This can be solved (for instance) with a recursive looping. The recursive looping work as per the following steps:
start the loop with an arbitrary wind pressure value (in this case 400N/m linear load on the members)
run the analysis
optimise the members
get the effective area of the members
send them back in the loop for wind load generation
repeat from step 2.
At the Anemone container we can define the number of loops (S). I found it sufficient to apply 6 loops in this case. After 4-5 loops no more optimisation is observed regarding the total weight of the structure.
One thing is also important to be mentioned. Since I am using Galapagos as evolutionary solver, I just did not want to run the loops manually. For an automated optimisation, one of the Galapagos input has been used as trigger for the Anemone loop. Which is a useful stuff ;) (I have tried HoopSnake before but without success)
Since my definition is part of a proprietary solution, I'm unable to share the .gh file. But I hope it still can give some hint what can be done by these components.
…
e existing wires.
2) The capsule display is very similar to the first graph, but instead of drawing a line connecting relative y-values for each slider, each slider get's assigned a colour (from dark red to yellow) based on it's relative position. It allows you to see whether two genomes are similar or not without taking up too many y pixels.
3) This is a tricky one to explain. Every genome in a single species has the same 'dimensionality'. For example, if there are only two sliders you can say that the entire genome space for the species is 2-dimensional. For every possible combination of these two sliders, there is a fitness value (or a height) on this two dimensional plane. If your genome consists of 6 sliders, then we're talking about a 6-dimensional space.
As you probably know, distances between points are computed with the same formula, regardless of the dimensions of these points. Pythagoras' method works for all points with identical and integer dimensions. So even though I cannot display a 6-dimensional genome space on a two-dimensional computer screen, I can compute the distances between all the genomes in a species/generation. This then gives me a matrix with the distances from every genome to every other genome. I translate this distance matrix to a node-spring particle system and solve that system in two-dimensions, which ultimately results in the point-scatter graph you see on the screen.
The axes of this 2D representation of the ND distances are meaningless. The absolute position of the points inside this grid are governed partly by chance. However the relative positions are meaningful in that they convey which genomes are similar and which ones are different. Points which appear close together represent similar genomes, points which appear far apart represent different genomes.
Basically it becomes very simple to see the entire collection of genomes and get a feel for how varied the set is. You can often even see sub-species appear as distinct clusters of points.
4) For every generation, I display the fittest genome (upper boundary of yellow area), the worst genome (lower boundary of yellow area), average genome fitness (the thick red line) and the standard deviation of the fitness distribution in both directions (the orange area). Everything below the average is hatched.
Have you seen the Blog entry about galapagos?
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 1:37pm on November 26, 2010
ign to every location in the space is the result of the fall-off equation. F/D² in the Metaball componenty, where D is the distance from the point to the location you're measuring and F is the scaling factor:
3) You repeat this for all the points, giving you a collection of revolved hyperbola:
4) Add the elevations for all hyperbolas together, just a simple A+B+C process:
5) You intersect this final landscape with a horizontal plane. The elevation of this plane corresponds with the iso-surface value. If we do it for a bunch of planes, you get the following result:
6) The interior of each slice represents the metaball, or rather the boundary of each slice:
That is the theory anyway, in order to actually get a speedy result the algorithm approaches the problem from a very different angle, but the result should be the same shape.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Rhino plugins to work in the mac version. As I understand it, what is holding up the GH making it over (fully) to the mac version is its dependence on the graphics libraries for Windows. There is no easy direct translation here, so, this is still under development. There is info spotted around the forum, you just need to dig deep enough to find it, and see that there is development of GH for Mac, but still, we should not hold our breath as there are significant hurdles to overcome. These hurdles are just technical, and should have a solution. Below are some references that point to the graphics issue I am discussing as well as a list from David where he does state that he is working on the Mac version.
Another positive note is that in Rhino 6, GH will be along for the ride...meaning (as I understand it) that we will not need to download GH after installation, it will be part of the Rhino install. I think this is a positive note as it means that GH will be more associated with the default Rhino experience, an experience which should carry over to the Mac version.
So, to sum up:
1. GH for Mac will probably happen.
2. Seems all of the code that does not depend on the graphic part (the logic in the components, Rhinocommon) already works in the mac.
3. Other Rhino plugins are already making their way to the Mac.
4. GH is becoming part of the default Rhino experience, and should probably carry over to the Mac experience.
5. Don't hold your breath. When it will happen is not under anyone's control necessarily. The solution needs to be practical in order for it to be rolled out.
My $0.02.
References:
http://www.grasshopper3d.com/forum/topics/partial-developer-absence?commentId=2985220%3AComment%3A929795&xg_source=activity
http://www.grasshopper3d.com/forum/topics/grasshopper-for-mac-update?xg_source=activity…