catch-all phrases that pick up all of the rest of it: you have inputs, algorithms, and outputs.
It sounds like you don't necessarily want to wade into the miasma of academic reflection on the terminology, but in case you're willing to hold your nose and brave it there is some fairly interesting stuff out there. Nick's point about computation versus computerization is pretty reflective of a common mode of thinking about it. AD published a book edited by Sean Ahlquist and Achim Menges a couple years back called "Computational Design Thinking" and their introduction lays out a compelling argument for the distinction. Likewise Philip Galanter's paper "What is Generative Art? Complexity Theory as a Context for Art Theory" is a good read.
I mean, ultimately it's about semantics. If you're worried about "real, accurate meaning" the reality is you're going to have to justify the boundaries of your own definition one way or another. David is rather a wry literalist who I suspect enjoys taking the piss out of academics, particularly when they're all puffed up (and really, every event is a form of computation if you want to go there). But usage counts, and there's a growing body of work staking claim to these terms, so it's better to know how and why if you even want to ask the question.…
Added by David Stasiuk at 2:01pm on November 28, 2013
Excellent knowledge of Rhino and Adobe Creative Suite (Photoshop, Illustrator, Indesign)
* Experience in Revit is preferred * Knowledge of Grasshopper is a plus
* Excellent communication and expression skills, fluency in spoken and written English is a must
* Good team player
Please apply with the official LAVA application manager and refer to this ad:
https://lava.poolarserver.com/quicklink/pageApplicationUpload.aspx
…
t the elements I used CreateHBsrfs and I added "Adiabatic" in the EPBC input. Since the EnergyPlus results weren't what I expected, I checked the idf file and I discovered none of the element is adiabatic. Furthermore, the simulation doesn't use the materials I set up for the not-adiabatic wall.
I even tryed with MakeAdiabatic, MakeAdiabaticbyname and MakeAdiabaticbytype. With the first and second the problem is still the same. With MakeAdiabaticbyType, if I change one wall type in the CreateHBsrfs, it still remains the same type in EnergyPlus, so it makes all the walls adiabatic. Is there something I can do? I attach the GH file Thanks in advance Lisa…
The type of recipe appears to be related to the problem, because de error desolves when I connect the component to a different recipe.
A screenshot of the complete error message is in the attachment.
Error text:
0. Annual climate-based analysis1. The component is checking ad, as, ar and aa values. This is just to make sure that the results are accurate enough.2. Good to go!3. Current working directory is set to: c:\ladybug\unnamed\annualSimulation\4. Rotating the scene for 41 degrees5. Runtime error (TypeErrorException): unsupported operand type(s) for +=: 'str' and 'bool'6. Traceback: line 6509, in transform, "<string>" line 1665, in writeRADAndMaterialFiles, "<string>" line 193, in main, "<string>" line 258, in script
Many thanks in advance…
er, i hae drawn a quck sketch. Different curves in blue and orange colour. i have marked on my sketch which is a a non-planar surface.
At the moment, i have modeled this with NURBS curve component (component without Knots & Weights). I have set 5 to its 'P' intput (I'm going to reduce it to 3). Each point having 3 parameters X, Y & X axis. I have set my slider from -100mm to 100mm range. It is a closed curve.
If i just loft it, i get random results which i donot want. I can get a planar surface if i set Z parameter to zero. But how do i get a non planar and preferably a burbs surface?
the curves are very important to this projects. as Whole form is dependent on these curves.
Your tips will be highly appreciated. If you have different way of modelling it, I'm open to suggestion too.
cheers,
aB…
and perpframes
3) Ellipse on perframes
4) Series + Move + Series + Scale + Series + rotate (to create generations)
5) Divide curve (ellipse) + Dispatch only seleced points + join those points on ellipse using Intercurve + Divide the resulting intercurve
6) List items (I used list items 4 times, you could do as many). For 'i' parameter in list item i used slider to create generations. depending upon your definition, at this stage you might have to flatten your list output
7) joint the points you get from list output to form another intercurve + repeat that for all items.
8) Loft the curve
9) to form fenestrations, i again used rhino closed curves.
8) Project curve onto surface + copy trim + surface to mesh + mesh thickening from WB.
Hope this helps
Cheers
aB
…
his project. Attached is my latest script. It seems to work for all points & directions of gravity except when the points are at equal height (in the reference plane the script creates, not in the world space). In other words, when the vector from A to B is perpendicular to the gravity vector, it doesn't work. It's totally due to the formulas used to solve for distance (see script), but I haven't found a way to fix it to make it work. Kudos to anyone that can help me figure it out!
Other notes: Required input: Point A, Point B, Gravity vector, and desired Height and/or desired chain/arch Length. Cool trick: when inputting both Height and Length, it recalculates the end point (point B) with those desired parameters, and the end point lies along the AB vector. Also, the "x" output shows either the found height, length, or distance (when both height & length are input), and "newPl" just shows the reference plane used to make calculations easier.
Cheers…
Added by Will McElwain at 11:52pm on January 18, 2014
med that a 1000 lux measurement for a particular hour on a workplane grid point will indicate a illuminance from direct sun at that point. If I remember correctly, these simulations are to be run without the presence of any shading devices.
From an ASE calculation perspective, there are several shortcomings within Daysim (as it exists right now). The daylight coefficient method, which Daysim employs, calculates illuminance by dividing the sky into discrete patches. (http://naturalfrequency.com/wiki/sky-subdivision) For a clear sky with sun, the luminance from sun is accounted for by approximating the position of sun into 3 (as far as I know) patches. That in turn leads to an incorrect estimation of both position and luminance contribution of the sun.
Anyways, as I wrote in the begining, in my opinion the closest you'd get to calculating ASE from daysim right now would be running an annual daylighting calculation with Honeybee by setting ambient bounces as zero. A better approach, in case you are not trying to comply with something like leed v4, would be to do a DGP analysis as Chris mentioned in his post.
…
i projected my surface on XY plane, created voronoi curves on the planar surface and re-project / map the curves onto the subject model.
However, i'm not getting a desired result.
can any-1 please help me. or even show me a different way to model it via GH? I donot want to use rhino objects.
I have attached my initial sketch, GH and Rhino files.
Hope to find some solution so I could move forward :-(
Moreover, I could not convert the initial non-planar curves into surface hence I converted them into Mesh (thanks to 'Brian Harms' for helping me out). However, the protruding edges of the mesh is not a smooth NURB curve, it forms kind of vertices of a polygon. Any way to smoothen / fillet it? Will it affect when i commence 3D printing?
Regards,
aB…
/ interest to some of you. I'm attempting to generate "bricks" along an arc, the span of the arc is known (Line AB), as is the desired brick edge length (shown as chords on the dotted circle). Im am essentially trying to solve for the diameter of the dotted circle and its center point (C). The variables within the grasshopper script would be span (X), chord Length (Y) and number of segments to the arch (N). Lacking the radius or central angle means that Im unable to solve this using my limited knowledge of Trig.
I guess the key issue here is that chord length and number is driving the radius of the arc / circle. Hence why Im not simply using the divide curve tool.
Any input members might have would be fantastic and I'd be very happy to share the resulting file.
Thank you!
…
Added by Robert Harvey at 11:24am on November 20, 2012