sando las nuevas tecnologías de la información en la arquitectura para la gestión del conocimiento de sistemas que desarrollen estructuras sustentables, desde los procesos de diseño generativos o algorítmicos. Donde se contempla la P.O.O. (programación orientada a objetos) como nuevo lenguaje de expresión para el arquitecto-diseñador en el siglo XXI.Los talleres están pensados para sigan un hilo conductual en el que al mismo tiempo que se enseña se investiga y experimenta. Por primera vez se contará con diversos miembros de SEED como docentes de forma presencial y por video conferencia, logrando de esta forma acercar a los especialistas que se encuentran en Europa a los asistentes de los talleres sin encarecer los costos.+info:http://www.studioseed.net/ adn-methodology/
Los talleres están dirigidos a personas que tengan o quieran conseguir un perfil alto de innovación, creatividad, flexibilidad: profesionales con actividades de dirección, gerencia, proyectistas, investigadores, así como a estudiantes a partir de 5to semestre en adelante. Cada taller abarca perfiles diversos de profesionales, mientras unos están más orientados a directivos y gerencias, otros más a proyectistas.
LOS TALLERES:FAB DIG I / ITESM – CEM / Estado de México / 20 hrs / 8 – 11 al de diciembre 2011 (En este taller no se aplican descuentos ni becas)PARAMETRIC GREEN HOUSING / Colegio de Arquitectos del estado de Jalisco (Por confirmar Sede) / Guadalajara / 20h + 5h proyecto / 30 enero 2012 al 4 de diciembre 2012FAB DIG II / ITESM – CEM / Estado de México / 30h + 5h proyecto / 8 a 12 febrero 2012TERCERA REVOLUCIÓN INDUSTRIAL: TIC`s + SOSTENIBILIDAD. Procesos y paradigmas emergentes / Querétaro / 20 hrs / 15 al 18 de febrero 2012INTRODUCCIÓN AL DISEÑO GENERATIVO / UAM-azc / DF / 8hrs / 13, 14 de enero (Costo representativo $650, máximo 40 personas, mínimo 15 personas)INTRODUCCIÓN A: SCRIPTING CON GRASSHOPPER ( Python) Y PLUGINS / Estudio SEED México / Estado de México / 30 hrs / 23, 24, 25 febrero y 1,2, 3 de marzo 2012…
Added by SEED studio at 3:30am on November 24, 2011
ly 26-27-28-29 (digital fabrication)
The third edition of digitalMed Workshop is structured as a design laboratory. Participants will learn the challenging process of producing ideas, projects and research analysis that are to be developed through specific software and concepts that emerge through the use of mapping, parametric design and digital fabrication.
The workshop will take place in the city of Salerno (Italy) and it will last 11 days structured into 3 intensive weekends: July 13-14-15 (mapping); July 19-20-21-22 (parametric design); July 26-27-28-29 (digital fabrication).
Goals and Objectives:
We aim to make clear the theoretical and technical knowledge in the approach to parametric and generative design and digital fabrication. (From collection and data management, to the manner in which these inform the geometries, to the fabrication of prototypes.)
Participants will also have the opportunity to practice the new knowledge gained in the design laboratory through project work.
Project Theme:
"Urban Field" Identify, study and analyze the system of public spaces in the urban area of the city of Salerno.
Connection, mutation, generation and evolution are the themes to be followed in project work.
Brief Description of Topics:
- Mapping. Our reality, in all its forms, has studied through concepts of the theory of Complex Systems. The techniques that will be used to study events and places of reality, will work for the management, manipulation and visualization of data and information. These will form the basis for project management and driven geometry, conducted during the second phase of the workshop.
- Parametric Design. Introduction to Rhino* and Grasshopper. Specifically, we will explain the concepts with which to work with the software of parametric design and how they function. Through these tools, we will arrive at the definition of systems of mathematical and / or geometrical relationships that are able to generate and govern patterns, shapes and objects that will inform the final design.
- Digital Fabrication. In this phase, participants of the workshop are organized into working groups. Participants have access to materials and conceptual apparatus that will take them directly to the fabrication of the geometries of the project, with the use of software CAD / CAM interface and the use of machines for the digital fabrication.
The DigitalMed workshop is organized by Nomad AREA (Academy of Research & Training in topics of Contemporary Architecture), in collaboration with the City of Salerno, the Order of Architects Province of Salerno and the National Institute of Architecture In / Arch - Campania.
Interested parties may download the Notice of Competition at the address www.digitalmedworkshop.com and fill the pre-registration no later than July 10th 2012.
PRESS OFFICE
Dr. Francesca Luciano
328 61 20 830
fra_luciano@libero.it
For information or subscriptions:
e-mail: info@digitalmedworkshop.com - tel: 089 463126 - 3391542980 …
tema della modellazione parametrica con Grasshopper. Questa plug-in di Rhino consente di progettare, confrontandosi con un contesto evolutivo, attraverso la comprensione e l'utilizzo di parametri e componenti che influenzano la rappresentazione e la rendono dinamica componendo algoritmi. Nel corso verranno introdotte le nozioni base di Grasshopper approfondendo le metodologie della progettazione parametrica e le tecniche di modellazione algoritmica per la generazione di forme complesse.
Le informazioni teoriche saranno fornite in maniera accelerata ma organica e contestuale agli argomenti elencati. Per massimizzare i risultati, le lezioni saranno accompagnate da piccole esercitazioni pratiche.Argomenti trattati:- Introduzione alla progettazione parametrica: teoria, esempi, casi studio- Grasshopper: concetti base, logica algoritmica, interfaccia grafica- Nozioni fondamentali: componenti, connessioni, data flow- Funzioni matematiche e logiche, serie, gestione dei dati- Analisi e definizione di curve e superfici- Definizione di griglie e pattern complessi- Trasformazioni geometriche, paneling- Attrattori, image sampler- Data tree: gestione di dati complessiStrutturaIl corso ha una durata di 16 ore programmate nell'arco di 2 giornate con i seguenti orari: i giorni 10/11 e 11/11 dalle 10,00 alle 19,00 con pausa pranzo di un'ora.
PrerequisitiPer affrontare il corso è richiesta una conoscenza di base del software Rhino attraverso esperienze teoriche e pratiche. I partecipanti dovranno venire muniti di proprio laptop e con software Rhinoceros 5 o Rhinocero 4 perfettamente funzionanti.Alla fine del corso, verrà rilasciato l’attestato di partecipazione ad un corso qualificato certificato dalla McNeel, valido anche per l’ottenimento di crediti formativi universitari.
…
t the maximum potential with the bridge BIM+PARAMETRIC DESIGN ;D
During this Intense Week, we will learn about the power of Rhino + Grasshopper + ArchiCAD with Professional and Useful examples for our Normal Working day :D
You will get Advanced Library Files + Personal Web + Knowledge and Skills to start using this incredible Methodology ;D
Also, the week is having Lectures from different Experts sharing their Computational Working Experiences ;D And Jam Sessions! opening the door to 5 interesting topics to research, learn and experiment together :D
2020 is your YEAR ;D !!!
Complete details and registration……
when I install Grasshopper, automatically install it in the folder rhino4. When I try to load it from Rhino 5 gives me the message that you can see in the add file.
Thanks
exchanging emails with Edmund on CAMel. But I haven't had time to study it yet (will do it tonight) or discuss with him in details.
Beaver & Lobster are also interesting, but I think they are aiming at something a bit higher right now, I focus more on getting the automation / batch process right at the moment. But I promise I'll look at them in details. Note I'm also interested in developing something up to 5 axis (head head) machine. Robotic arm is a bit too much for me, since I aim at creating a plugin more for batch production and real construction more then experimental stuff (since most experimental researchers are able program routines that they need any ways)
Time Estimation - Yea Mach3 is a nice driver. But I start to think that most CNC programmer or even operator don't know how their machine were actually configured. Not many people know what motion profiles, look ahead or even acceleration. So I don't know how the acceleration profile could be a setting that a general programmer could enter and get an good estimation. /// One way of getting a more precise estimation is to use a simple trapezoidal speed profile and make a guess. /// Another way is to just sum up the speed X distance (Even CATIA and MadCAM do it this way.)
The file you have uploaded, 2dPartsGeneratorTest.rar, I couldn't download it from the forum's server, seems to be a problem with the rar file format. I can download your .gh, but I can't understand it without the Rhino file. And sorry, I also have only Rhino 4, no money at the moment.
Outline Extractor? Can you explain more?
I had difficulty making good and reliable offsets with some 2D curve input, I'm not sure if it is a Rhino 4 problem or if the new RHino SKD haven't improved that yet.
I do not have intent to overlap with RhinoNest, RhinoNest is already nicely developed with integration with GH, I think RhinoNest or other Nesting software users can easily perform nesting in Rhino or in GH (such as RhinoNest in GH) and the results are fed to this package.
Thanks a lot for your info.
…
e to subscribe to the same set of rules of course, but things I like to do when programming are:
Declare variables as late as possible. Don't put them all at the top, but put them on the line above the first line that uses them.
Give variables understandable names. "curves" is to be preferred to "crvs" or "c".
Don't nest conditional structures too deep. If there's no way around it, move inner loops into their own functions. A great way to reduce too much indentation is to write:If (Not x) Then Continue For
Instead of
If (x) Then blahblahblahEnd If
Always check for null/Nothing if you get a reference type from some process.
Always check for empty arrays.
Use ReadOnly class level variables whenever possible.
Import few namespaces. Basically, don't import any unless you have to specifically refer to a namespace, say, more than 5 times.
Use #Regions to combine properties, constructors/destructors and other closely related methods.
Prefix class level variables with m_. This is in fact an archaic rule borrowed from Hungarian notation which is not recommended by the .NET style guide any more, but I like it.
Don't compare booleans to True or False in conditionals, i.e.If (x = True) ThenIf (x = False) Then
should be
If (x) ThenIf (Not x) Then
Put the conditional statements in If blocks in brackets.
Use AndAlso and OrElse instead of And and Or whenever possible.
Use String.Format() instead of &'s to combine strings.
Use constants like String.Empty and Vector3d.XAxis instead of "" and New Vector3d(1,0,0)
When comparing strings, use the .Equals() method with the proper StringComparison instead of =.
It also seems like the algorithm you're using is pretty sensitive. I'm not exactly certain what your input is supposed to look like, but I think it can be made more robust.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
ting up but I’m glad the discussion has been rolling!
I understand what you mean, Abraham with property boundary rights and I’ll admit that I can potentially see some usefulness in what you are suggesting with the solar envelope. For example, I could imagine this integrated into the component as a "trimWithSiteBoundary" boolean input that a user could flip if they are only interested in seeing what is going above their property boundary. However, I have a big fear that new users might not fully understand what this operation is doing if they are first encountering my component and would therefore end up with a misleading result. In other words, I would like users to see the complete solar geometry before they trim it with the site boundary extrusion so that they are fully aware of what is going on. Also, because this trimming operation is very easy to set up with existing grasshopper components (you were able to do it yourself pretty easily in the file that you uploaded), I would rather have users employ this method rather than having something built into the component.
As for the solar fan suggestion, I think that filling in that portion of the fan would just be too misleading. I could all-too-easily see new users making the mistake of saying that a neighbor’s cantilever over the north part of their site blocks their sun, which is simply not true. Also, there is the argument that this operation (if the user really wants it) should be very easy to set up with existing grasshopper components. However, I see that in your uploaded GH file, this has not been working correctl. I have been playing around with it for the last hour and I am pretty confident that you have found a bug in Grasshopper that I will report to Guilio shortly. In the meantime, I have uploaded a new file in which you are able to get the type of solar fan that you desire. I will try to keep you posted.
As Mostapha and Saeran have suggested, I think things would be best if we press forward with having my component useful for very detailed lengthy solar fan/envelope analysis and Saeran’s component useful for quick, initial analysis. By the way, Saeran, I am really impressed with the speed of your component, especially for the solar envelope. I like the methodology you used and it’s a huge asset to the Ladybug suite.
Thanks again, Abraham, for all of the feedback and I hope that you are able to get a lot of use out of these components.
-Chris…
ecific than the thread title...
and here i have a generic application of this approach to surfaces created by a two dimentional "sketch" of kd tree from a random float, extruded z direction. i did using only grasshopper components for now.
but then i have to analyze the surface curvature because any tangent circle on the surface should have less than 5 cm diameter. so when i get a mesh i want analyze, it has like 400k faces at the moment. when i intersect this mesh with plane every 1cm or so, the mesh intersection work in no time, but then i wont get to the end of joining all the little lines into curves.
its the curves of the surface i need so that i can interpolate the points using discontinuity components, evaluate curve, tangent circle and cull the circles by diameters to see where the surface design can cause material to damage or have cosmetic defects.
i was hoping to use either galapagos or octopus to minimize the numbers of the tangent circles that exceed 5cms on the surfaces, once i have recorded a kangaroo simulation run, rather than having to run and rerun kangaroo for surfaces individually to simulate and analyze the mesh outputs.
when i design the support structure for the panels that depends on the shape of each panel, I also want to see the total material length of the support structures and its efficiency before i make any changes to the initial control brep (show in green, blue, pink and white)
for me its important to show how it is possible for the initial floats to be altered (like the swarm behavior, or some other algorithms) and have the entire process reset, analyze and record data. because the sheet material is a formable but NOT FLEXIBLE material which can take on many possible shapes, i wanted to create a definition robust enough for many iterations and for me to be able to navigate between the possibilities. …
loudy) sky it should be 50%.
For each case I get close to those numbers but not those numbers. I get around 38 for the CIE and and 48.something for the uniform sky.
Also I would expect that for each window, which has the center point above the roof or the context they would all get the maximum value, irrelevant also of their horizontal location,which is not the case (they have very slight deviations).
Radiance uses a stochastic method for lighting simulation and up to 5% tolerance in the results even for the same case is normal. Just re-run the analysis couple of times and you will see the numbers will slightly change. You will get 49.something in couple of tries.
Also I noticed that I have to reconnect the ptsFileAddress input each time I change the testSurface objects, but probably this is an expected behavior.
In case you are using searchAnnual component to read the results, connect done output to refresh input so the results will be updated automatically.
are you considering of adding a Radiance Folder Output to the runDaylightAnalysis so we don't repeat with text Concatenation the folder location manually?
It is already there. gridBasedResultFiles outputs the file address. Sorry if the example file was confusing. In that example I wanted to make it clear that you can reproduce all the results from the study folder. I intentionally made the result visualization harder than what it can be to make sure users will educate themselves about the outputs but not as hard as what you have been doing. Sorry! :)
Check the attached file for a revised version of your file.
…