een them to be adiabatic (at first. See later on for an alternative).
The whole process is fine/clear up to the solveAdjacencies: The walls are defined as "outdoors" and "surface" for the boundary conditions. So far so good.
Now i get to the HB_makeAdiabaticByType, and some issues appear (See A in the file).
Setting the interiorWalls to True doesn't change the condition from"surface" to "adiabatic" (A1 in file).
Setting the walls set both internal and external, to adiabatic (A2 in file). Is this supposed to work like this? Why the just the internal doesn't make the change?
In addition to this i'll appreciate your advice in the following. Let's say that i want the internal walls to be divided in 2 parts each. One should be adiabatic and the other "air wall". How do you recommend to do this? Is the modeling in the file correct, or i must do surface by surface?Or using the Decompose Honeybee Zone ...?
How can i retain the air walls and still use the makeAdiabaticByType component?
Thanks for your help!!
-A.
…
ion technologies offer a completely new way to think and approach design, architecture and urban planning.
. . .
The ADVANCED ARCHITECTURE SUMMER SCHOOL organised in Paris by VOLUMES coworking, NOUMENA architecture and architect/teacher/designer Francesco Cingolani in partnership with the prestigious École Nationale des Ponts et Chaussées is a 3 weeks learning experience designed as an immersive journey in social innovation, computational design, digital fabrication and collaborative culture.
Details and informations for applicants> volumesparis.org/summerschool2015…
r).
http://www.agrob-buchtal.de/en/cd/produkte/produkte_seiten_13045.ht...
2. 1 puts some "modular Z" increment puzzles (for more than obvious reasons). Additionally the excavation cost VS any ECO-benefits ... (heat exchangers in the foundation blah blah). OK that means that the footprint it's also modular., not to mention the whole composition (potentially).
3. So: use the projection ONLY for defining where a given footprint meets the terrain (see the yellow and blue things in V2) and then LOFT pairs (see PlanA, B) of profiles into 2 DISTINCT portions ("solids" so to speak): (a) the basement (or at least something where some potential partitions could being classified as "underground" spaces), (b) the classic building.
4. By doing 3 ... keep an eye on 2 as well (Don't forget the classic minor terrain "adjustments" around each building (meaning usage or "tmp" solids), access roads/pavements (ditto), potential connection of basements (parking), soil stabilization issues, bad seismic behavior on unevenly(Z) formed basements etc etc).…
tting-edge results at the interface of geometry processing and architectural design. Scientific chairs of the conference are Lars Hesselgren, Shrikant Sharma, and Johannes Wallner. Keynote speakers are: Pierre Alliez, INRIA Sophia-Antipolis Philip Ball, Physicist and science writer Chuck Hoberman, Hoberman Associates Jan Knippers, Knippers Helbig Advanced Engineering
We are happy to announce that public lectures will be held by Toyo Ito and Mutsuro Sasaki. The organization is cordially inviting you to contribute a paper or a workshop, or simply to visit. More details concerning registration and submission can be found on the conference web page at http://aag12.architecturalgeometry.at/. The submission deadline has recently been extended.
This conference receives funding from the ECs Seventh Framework Programme under grant agreement number 230520. Thanks to this funding we are able to cover the registration fees and support the travel expenses of 20 young participants. Places will be distributed among those who submit a poster, paper or workshop proposal.…
per space. In the upper right corner you draw another dot, and you write "1, 1" next to it. You now have 2 points defined in paper space (uv space).
Ok, lay down the pencil and pick up the paper. You'll notice that the two points have just moved through world-space. They were very close to the desk, but now they are hovering above it. The coordinates you wrote down on the paper or the other hand are still valid.
No matter what you do to this piece of paper; crumple it, fold it, take it on a plane to South Africa, those two points remain fixed in paper space.
A surface is always a rectangle in Rhino. It may be deformed, it may have holes cut into it, but in the end it's always a rectangle, just like your piece of paper. UV coordinates are points that are defined in Surface UV space. They consist of only two numbers, because a surface has no thickness. At any point in time, you can translate these UV points into World XYZ points using what is called a surface evaluator. Where these XYZ points end up depends entirely on the *shape*, *size* and *location* of the surface.
----
Surface uv-space (and Curve t-space) are vital when dealing with nurbs geometry. If you do not understand the concept of parameter space, you will have a lot of problems because many components in Grasshopper use these coordinates.
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 6:40pm on September 27, 2009
, and made the below definition to try it out. (lots of components to draw a line, but I'm just trying to understand the equation)
I had been searching for advice on some geometry topics worth exploring for a class, and now I'm in the class and the teacher wants me to start by learning about splines in general (not nurbs). I just spent the day learning linear spline interpolation, then quadratic, then cubic. I didn't try working them by hand yet, but I'm getting the concepts. It seems cubic is the lowest degree where you can get C2 continuity, which makes it smooth. I read over parameterization and how that simplifies the number of equations. I read about space curves, and then the differences between Hermite, Catmull-Rom, and Cardinal spline, but then got tired and had a cocktail.
So I guess I'm looking for any direction or advice on how to understand parametric curves in 3d space, and how they can be defined (splines or otherwise). Thanks!!!
…
creating the structural frame, finding the endpoints, linking these endpoints with curves and afterwards lofting the surfaces between the curves.
The results were quite nice, however, the procedure is very time consuming and inefficient. There is just too much copy-pasting involved.
(see attached file: "Old Attempts.zip" )
Mesh relaxation:
I have later on used Daniel Piker's tutorials on Mesh Relaxation and realized that this might be the way to go.
The link to these online tutorials on wewanttolearn.net is:
https://wewanttolearn.wordpress.com/2011/10/22/mesh-relaxation-kangaroo-tutorial/
His tutorials, however, only deal with mesh boxes which are ideal cubes. He then joins them together in various directions, but it is under 90 degrees angle.
( see attached file: "Daniel Pikers Examples" )
What I would like to achieve:
I want my bridges to go in all directions and angles, not just under 90 degree angle.
Ideally I would like to make a square (polygon) follow a curve (which moves in all axis) at certain number of division points. I would then loft these squares into a mesh and use that shape as a mesh box. I would later use this mesh box and relax it the same way as Daniel Piker used the cubes in his tutorial. The anchor points are only the vertices of the squares which create the lofted mesh box.
( see attached file: "New Attempts" )
As you can see below this procedure works even if the curve is moving in all directions not only along xy axis. There are, however, many problems connected to it.
The problem:
Despite all the effort I cannot seem to come up with a design where I would be able to draw a random curve which would be the guideline for my mesh box and then apply this box to one definition in order to relax the mesh and create the shape that I want. Without this I am again forced into a lot of copy pasting as the final mesh box is made out of several sections.
Also is there any way I could make the final resulting mesh a bit smoother? Increasing the number of mesh faces is probably the only way, right?
Thank you guys so much for any potential help.
All best,
Luka
…
) function if you've already got a boolean value.
This expression:
x < 12
results in exactly the same things as this expression:
If( x < 12, True, False )
If() is only really useful when you want to return non-boolean data, like so:
If( x < 12, x, 100-x )
In this case, the expression will return either x, or 100-x if x is larger than or equal to 12:
x result
1 1
2 2
10 10
11 11
12 88
13 87
14 86
18 82
70 30
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 7:22am on August 10, 2011