uired information, a poor representation of data evolve misreading messages and by turn ambiguous responses especially with complex data. Inforgraphics are graphic visual representations of information, data or knowledge intended to present complex information quickly and clearly. In the nowadays flow of complex information, Infographics is the key for optimized visual communication. The use of infographics is an important step towards developing a pedagogical approach that draws on visuals where 90% of Information is transmitted to the brain so it is crucial to tickle the optic nerves to get people excited about data. The workshop investigates how computational tools can aid in designing and controlling complex information to be easily understood in addition to improve cognition by utilizing graphics to enhance the human visual system’s ability to see patterns and trends and much more likely to be remembered in today’s fast – paced environment. This workshop investigates multiple computational tools and techniques of developing coefficient visualization of data types including; network, statistical and hierarchal data. The workshop objective is to reconsider visual representation a promising design tool for architects, artists and designers. /// Application To apply, please follow this link to fill the application form https://docs.google.com/forms/d/1HOv6c1_LzhHNJU5n_FLvuhC-Yg75HDfbEcq6TN6mulI/viewform /// Fees 1200 EGP for students / 1500 EGP for graduates and young professionals more info on the workshop webpage: http://www.encodestudio.net/#!infographics/cqvl
POSTS
…
ogue script I wrote. Again, apologies for the false alert.
However the comparison for solar gains between IES and HoneyBee still stands. I get an average error of roughly 25% in the Summer (when I account for daylight savings) where HoneyBee is underestimating compared to IES. In the Winter both results are very similar but gradually deteriorate as they go into the summer. I have constructed a fairly simple window and expected only the G-value (SHGC) to affect solar gains. In both programs there is only 1 south facing window (9.6m2) with a G-value of 0.4. Is making a window out of 1 layer of glass the issue?
Other quick question, is there any way to make EnergyPlus model with daylight savings through HoneyBee?
I'm also having trouble with natural ventilation (maybe I should post this in a different conversation?), I have set up the windows to open for the same interior and exterior temperature conditions and with the exact same infiltration+auxiliary vent rates but results are very different. Auxiliary vent and infiltration are the same throughout the entire year but whenever the windows open it seems HoneyBee calculates higher flow rates. Windows in both models also have the same operable area (10%).
I thought maybe the windows weren't opening right for some reason so I created a schedule from the IES window opening to limit the degree of opening of the windows but the results were still very off. Any ideas what might be causing this?
I realise this is quite a mouthfull of stuff to go through, sorry about that, but I've attached the file I'm modelling with as well as the excel sheet I'm writing my results to. I'm also using Bumblebee to read/write data from/to excel.
Thank you!
Antoine…
et us consider a plane somewhere in space, 10 units along each side, and it has UV domains 0-1 in both directions. It's a perfect square surface basically.
This surface only really 'exists' on the inside of the UV domains. You can evaluate the surface at {0,0}, which will give you the lower left corner, you can evaluate it at {1,1}, which will give you the upper right corner or you can evaluate it at {0.5, 0.5} which might give you the point in the middle. If you evaluate it at {2,-5}, you will get a point that is beyond the surface edge.
This surface 'space' is strictly two-dimensional and it is also bounded, meaning it has a finite region in which things can be said to exist. If we attach a point to this surface at UV coordinates {0.5, 0.5}, then move the surface about, the point will move with the surface. So it's XYZ coordinates will change, but the UV coordinates are still {0.5, 0.5}! These are just two ways of looking at the same point. Either we treat the point as a coordinate in infinite 3D euclidean space {x,y,z} or we treat it as anchored to a surface {u,v}. Going from XYZ to UV is usually called "Projecting" or "Pulling", going from UV to XYZ is usually called "Evaluating" or "Sampling", but they are mathematically very similar processes.
Evan mentioned that Voronoi only works in the flat 2D plane. He suggested remapping the points from the surface onto the World XY plane, then solving the Voronoi diagram, then mapping the result back onto the surface again.
Basically that means projecting all your XYZ points to surface UV space. That will give you a collection of points defined strictly by 2 coordinates, i.e. it is completely flat. You solve the Voronoi diagram on these flat points, and then you have to put the flat points (and the flat voronoi cell outlines) back onto the surface.
Have a look at the [Surface CP] and [Evaluate Surface] components, they provide the methods required to map coordinates from XYZ space to UV space and vice versa.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 12:51pm on April 29, 2010
Meeting Agenda:
1) Discuss what the group would like to learn this term through our regular scheduled meetings. Topics include the priority and sequence of Grasshopper exercises we would like to explore during the winter term from http://www.digitaltoolbox.info/grasshopper_basic.html and Processing tutorials from the Processing Handbook I received from MIT.
2) Watch the Matt Storus Church Machine video and have a discussion about parametric and generative tools in design.
If you have a chance, please read the following article by Tim Love called Between Mission Statement and Parametric Model at:
http://places.designobserver.com/entry.html?entry=10757
3) Discuss a possible design build project over the following winter and spring terms using the skill set this group is developing. Conversation led by Chris Nielson (please see comments below for a brief backstory)
4) Discuss possible applied research and design work for the National Conference on the Beginning Design Student paper, Machine Craft and the Contemporary Designer: exploring parameters and variables through making physical artifacts. I wrote the attached abstract and submitted it for the conference the past fall and it was accepted. To continue with the research I need to assemble a team of students that will help explore the principles I set forth by making physical objects with the cnc router. In exchange for helping with the research I will show participants how to use the cnc router, how to author machine code and provide you with the cnc controller interface software necessary to simulate machine movements. Not to mention, your work will be sited in the research paper I present at the conference at UNC Charlotte in March. More tomorrow night, of course.
Thank you for your interest and I hope to see you there.
Sincerely,
Erik Hegre
Chris Nielson Reply by Eugene Parametric Society on January 7, 2010 at 12:02pm
All,
In response to Erik, who requested that I describe my intentions in a design-build project and to the article posted (definitely required reading for this group) I propose that we begin development of a project that spans the realm of "sustainable social" architecture and parametric design. The particulars of such a design do need to be made concrete, and it will be important to define the goals of such a project.
Therefore, I would suggest that this serve as a forum for the next few weeks for those interested in producing a built project. I agree with Nico that it may not be feasible to create the built piece, whatever it may be, this term; however we should have the groundwork and a plan in place by the end of the next 10 weeks.
Either way, I would ask that everyone who is interested to please provide as many concepts to this forum to begin a discussion. If you are indeed interested, please submit goals that this project could achieve (energy, socially, aesthetically, economically, related) and perhaps what you envision the project to physically be (shading device, public bench, water catchment, interactive thermal contraption, etc . . . )
I look forward to hearing your thoughts!
Cheers,
Christopher…
Send Feedback
Defines enumerated values for all implemented corner styles in curve offsets.
Namespace: Rhino.GeometryAssembly: RhinoCommon (in RhinoCommon.dll) Version: 5.1.30000.12 (5.0.20693.0)
Syntax
C#
public enum CurveOffsetCornerStyle
Visual Basic
Public Enumeration CurveOffsetCornerStyle
Members
Member name
Value
Description
None
0
The dafault value.
Sharp
1
Offsets and extends curves with a straight line until they intersect.
Round
2
Offsets and fillets curves with an arc of radius equal to the offset distance.
Smooth
3
Offsets and connects curves with a smooth (G1 continuity) curve.
Chamfer
4
Offsets and connects curves with a straight line between their endpoints.
…
changes is the usage of Structures ("ValueTypes" as they are known in generic .NET parlance) over Classes. In the old SDK On3dPoint was a class. That means that if you declare an On3dPoint, it would be Nothing:
Dim pt As On3dPoint 'This results in a pt which doesn't exist, i.e. Nothing
Attempting to call any functions on this would result in a NullReferenceException. Point3d in RhinoCommon is a structure, very much like the integer and boolean types. It is impossible for a structure to not exist. Therefore, when you declare a Point3d, you actually get a valid point at {0,0,0}:
Dim pt As Point3d 'This results in a point at {0,0,0}
The difference between structures and classes ("value types" and "reference types" respectively) is very important and you'll need to understand it otherwise you'll keep running into weird bugs you can't explain. One of the biggest differences to keep in mind is that assigning a Value Type to another Value Type automatically creates a copy of it. Observe these two pieces of code:
Dim pt0 As New On3dPoint(1,4,0)
Dim pt1 As On3dPoint = pt0
pt1.Z = 10
vs.
Dim pt2 As New Point3d(1,4,0)
Dim pt3 As Point3d = pt2
pt3.Z = 10
The first example uses On3dPoint, which is a reference type. "Reference" means that the actual data stored inside the pt0 and pt1 variables is in fact a memory address. When you then try to access the Z component of the point, the computer will read that memory address stored inside the variable, go to that location in memory and extract the number at that location that represents the Z component of the point. So On3dPoints exist somewhere in memory (you don't know where and you shouldn't have to care) and you can have any number of On3dPoint references pointing to that address, i.e. all sharing the same point data.
Not so with value types. Value types don't store their data elsewhere and then remember where elsewhere is supposed to be, they store their data directly inside the variable. So when you assign pt0 to pt1, what's actually happening is that the reference to the On3dPoint instance is copied, and now pt0 and pt1 both point at the same location in memory. Therefore changing the Z of pt1 will also change the Z of pt0, since they're the same Z. However when you assign pt2 to pt3, it also assigns the data inside pt2 to pt3, but in this case the data is in fact the point coordinate itself. So changing the Z of pt3 does not affect the Z of pt2.
Because of this fundamental difference between the old and the new points* you cannot simply translate code, you need to really understand what the code is doing in order to rewrite it. My guess in this case is that you're trying to call a constructor that doesn't exist:
Dim pt As New Point3d(pts(n))
In the old SDK the best way to create a copy of a point was to use the copy-constructor. However this constructor is missing in RhinoCommon because simply assigning the old point has the same effect:
Dim pt As Point3d = pts(n)
* Vectors, Planes, Transform matrices, Circles, Arcs, Lines etc. are also all Value Types in RhinoCommon
--
David Rutten
david@mcneel.com
Poprad, Slovakia
…
Added by David Rutten at 2:19am on January 15, 2012
quired)
// Agenda
Parametric Design, in the history of architecture, has defined many rules for current designers and for future practitioners to follow. One of the strongest aspects that are prominent from this style is ‘geometry’. Arguably, there is nothing new about geometry and aesthetics forming the most prominent aspect of any style or era. The language of any style, in the long history of architecture, is visually defined by geometry or shape, beyond the principles that define the core of the style. In the distinguishable style of parametric architecture, geometry has played and is continuing to play an integral role. And with this fairly young style, there are many strings of myths and false notions associated.
The workshop aims to provide a detailed insight to ‘parametric design’ and embedded logics behind it through a series of design explorations using Rhinoceros & Grasshopper platforms, along with understanding of data-driven fabrication strategies. An insight to Computational Design and its subsets of Parametric Design, Algorithmic Design, Generative Design and Evolutionary Design will be provided through presentations, technical sessions & studio work, with highlighting agenda of using data into Hands-on fabrication of a parametrically generated design. A strong focus will be made on ‘geometry’ and ‘matter’.
Day 1 Topics / Agenda
Rhinoceros 3D GUI and basic use
Installing Grasshopper & plug-ins
Grasshopper GUI
Basic logic, components, parameters, inputs, numbers, simple geometry, referenced geometry, locally defined geometry, baking, etc.
Lists & Data Tree: management, manipulation, visualization, etc.
Design Experimentations with Geometry & Data
Understanding Data for Manual Fabrication
Day 2 Topics / Agenda
Design Experimentations with Geometry, Form, Matter
Data for effective numbering and strategizing during Manual Fabrication
Collaborative effort for Hands-on ‘making’ process
Analysis & Evaluation of Fabricated Geometry
Documentation
// Tutor(s): Sushant Verma (Architect / Computational Designer / Educator)
…
en la práctica de nuevos métodos de diseño y fabricación utilizando herramientas digitales. Estos procedimientos emergentes están cambiando radicalmente la manera en que nos aproximamos al proceso de diseño en términos de concepción y producción. Los participantes serán introducidos en el uso de softwares de modelado 2d y 3d para la generación de geometrías que serán posteriormente mecanizadas in situ en una máquina de control numérico CNC de 3 ejes.
¡AL FINAL DEL CURSO TE LLEVAS TU LÁMPARA A CASA!
Profesores: Equipo MEDIODESIGN* + TOOLINGROUP*
*Official Rhino Trainners. Acreditación otorgada por McNeel, desarrolladores del software Rhinoceros.
Lugar: Mediodesign. Pallars 85-91 5-2 BCN
Duración: 16 / 20 horas
Fecha: sábado 9 / domingo 10 julio de 2011
Horario: de 10h a 14h / de 16h a 20h
Plazas: 20 participantes
REQUISITOS
< Dirigido a estudiantes y profesionales de la arquitectura, diseño y profesiones afines.
< Ordenador portátil.
< Softwares instalados. En el momento de la inscripción, los participantes recibirán las instrucciones para la descarga e instalación de versiones gratuitas (trials) de los softwares.
CONTENIDOS
< Introducción al diseño avanzado y la fabricación digital.
< Entorno Rhinoceros y sus plug-ins.
< Herramientas y estrategias de trabajo CNC.
< Materiales y sus características.
< Planteamiento del ejercicio: diseño de una luminaria
< Desarrollo del archivo de RhinoCam para el mecanizado CNC.
< Mecanizado y post-producción.
< Entrega de propuestas: Presentación en formato digital del proceso de diseño y fabricación (pdf, powerpoint, etc…) y del prototipo de luminaria realizado.
INSCRIPCIONES
Precio: 199 € Materiales incluidos.
Forma de pago: mediante transferencia bancaria.
Límite fecha de inscripción: lunes 4 de julio 2011
Se otorgará certificado de asistencia. …
up structural systems in the parametric environment of Grasshopper. Participants will be guided through the basics of analysing and interpreting structural models, to optimisation processes and how to integrate Karamba3d into C# scripts.
This workshop is aimed towards beginner to intermediate users of Karamba however advanced users are also encouraged to apply. It is open to both professional and academic users.
Course Fee:
Professional EUR 750 (+VAT)
Educational EUR 375 (+VAT)
Course Outline
Introduction & Presentation of project examples
Optimization of cross sections of line based and surface based elements
Geometric Optimization
Topological Optimization
Structural Performance Informed Form Finding
Understanding analysis algorithms embedded in Karamba and visualising results
Complex Workflow processes in Rhino3d, Grasshopper3d and Karamba3d
Places are limited to a maximum of 10 participants with limited educational places. A minimum of 4 places are required for the workshop to take place.
The workshop will be cancelled should this quota not be filled by May 31st.
The workshop will be taught in English. Basic Rhino and Grasshopper knowledge is recommended. No knowledge of Karamba is needed.
Participants should bring their own laptops with either Rhino5/Rhino6 and Grasshopper3d installed. A 90 day trial version of Rhino can be downloaded from Rhino3d.
Karamba ½ year licenses for non-commercial use will be provided to all participants.
…
up structural systems in the parametric environment of Grasshopper. Participants will be guided through the basics of analysing and interpreting structural models, to optimisation processes and how to integrate Karamba3d into C# scripts.
This workshop is aimed towards beginner to intermediate users of Karamba however advanced users are also encouraged to apply. It is open to both professional and academic users.
Course Fee:
Professional EUR 750 (+VAT)
Student EUR 375 (+VAT)
Course Outline
Introduction & Presentation of project examples
Optimization of cross sections of line based and surface based elements
Geometric Optimization
Topological Optimization
Structural Performance Informed Form Finding
Understanding analysis algorithms embedded in Karamba and visualising results
Complex Workflow processes in Rhino3d, Grasshopper3d and Karamba3d
Places are limited to a maximum of 10 participants with limited educational places. A minimum of 4 places are required for the workshop to take place.
The workshop will be cancelled should this quota not be filled by October 15th.
The workshop will be taught in English. Basic Rhino and Grasshopper knowledge is recommended. No knowledge of Karamba is needed.
Participants should bring their own laptops with either Rhino5/Rhino6 and Grasshopper3d installed. A 90 day trial version of Rhino can be downloaded from Rhino3d.
Karamba ½ year licenses for non-commercial use will be provided to all participants.
…