- nickname is rather the best approach - and not on active group, but that's irrelevant anyway).
Step back (assuming that you are talking about the "Tens_from_random_blah_blah" definition):
1. Engineering is the art of demystifying (or we are promising that anyway, he he). This means that you start defining (better: outlining) some topology for things based on some "generic" rules (like the ones applied for the masts,cables,cones etc etc). These things are kept in some kind of structure (Lists, DataTrees etc). Things are few in 99.99999% of cases (i.e. : even the biggest membrane "module" has, say, 20-50 masts per "module").
2. Then ... handling things "individually" (mostly modifying) becomes the most critical part. See this (an x "possible" solution by combining a myriad of "options" : a no cones membrane solution, in plain English):
3. But the above is impossible (for more than obvious reasons). You should deploy masts in some high/low sequence in order to achieve some meaningful convex/concave formation that could work.
4. This "works" : 5. This doesn't:
6. This works partially (the formation at the back is "flat" == undo able):
7. This is utterly kitsch (and faulty as the case6 - the back portion):
So it's quite obvious that without a (quite complex) capability to individually control things (in this occasion : mast heights) the whole definition is a waste of computer time. Additionally the more the solution is "demystified" (some curve is defined, some random points are created, some masts are in place, some cables appear etc etc) the more additional constrains are required in order to "narrow" the possibilities (In plain English : sliders should control other sliders as regards their min/max values, true/false, you/me etc etc).
Remember that we are talking about ONE (mast height) out of a myriad things that you should control "manually" (it's utterly pointless to mastermind some kind of "generic" rules - or use naive attractors etc etc) .You'll see the difference when I'll completely reform the definition by adding individual control upon anything.
PS: what about the blocks? (the real life stuff that actually make any solution possible). Can you imagine a 2nd set of "restrictions" imposed by "a child to his parent"? (Assembly/Component modeling , that is).
more soon
…
uick answers. Below you will find some suggestions, but don't think of them as rules and especially don't think of them as guarantees.
1. Choose a descriptive title for your post
Don't call your question "Help!" or "I have a problem" or "Deadline tonight!", but actually describe the problem you are having.
2. Be succinct but clear in your wording
People need to know some details about your problem in order to understand what sort of answers would satisfy you, but nobody cares about how angry your boss or how bad your teacher or how tight your deadline is. Talk about the problem and only the problem. If you don't speak English well, you should probably post in your native language as well as providing a Google Translation of your question.
3. Attach minimal versions of all the relevant files
If you have a GH/GHX file you have a question about, attach it to the post. Don't expect that people will recreate a file based on a screen-shot because that's a lot of pointless work. It's also a good idea to remove everything non-essential from a GH file. You can use the 'Internalise Data' menu option to cut everything to the left of a parameter:
If you're importing curves or Breps or meshes from Rhino, you can also internalise them so you won't have to post a 3DM file as well as a GH file. If you do attach large files, consider zipping them first. Do not use RAR, Ning doesn't handle it.
It is especially a good idea to post files that don't require any non-standard components if at all possible. Not everyone has Kangaroo or Hoopsnake or Geco installed so if your file relies on those components, it might not open correctly elsewhere.
4. Include a detailed image of the GH file if it makes sense
If your question is about a specific (group of) components, consider adding a screenshot of the file in the text of the post. You can use the Ctrl+Shift+Q feature in Grasshopper to quickly create nice screenshots with focus rectangles such as this:
5. Include links to online resources if possible
If you have a question about Schwarz Minimal surfaces, please link to a website which talks about these.
6. Create new topics rather than continuing old ones
It's usually better to start a fresh question, even if there's already a discussion that kinda sorta tangentially touches upon the same issue. Please link to that discussion, but start anew.
7. This is not a 'do my work for me' group
Many of us like to help, but it's good to see effort on our part being matched by effort on your part. Questions in the form of 'I need to do X but cannot be bothered to try and learn the software' will (and should) go unanswered.
7b. Similarly, questions in the form of 'How do I quickly recreate this facade that took a team of skilled professionals four months to figure out?' have a very low success rate.
--
David Rutten
Lead Grasshopper Development
Robert McNeel & Associates…
Added by David Rutten at 12:58pm on October 1, 2013
cálculos de otra manera imposibles de llevarse a cabo. La idea es mostrar una introducción a estos plugins explicando su funcionamiento general, ventajas y características con una serie de ejercicios prácticos a modo de ejemplo.
De esta manera se hará hincapié en conceptos muy presentes en el diseño e ingeniería avanzada: topología, form-finding, optimización estructural, fractales, loop, algoritmos genéticos y repetitivos, etc.
También, se dedicará un tiempo para sacar partido a tus definiciones y hacer más atractivo el diseño. Esto es, con una correcta exportación, animaciones, vistas...
ESTRUCTURA
- Geometría interactiva flexible
- Diseño generativo
- Reacción difusión
- Geometría desde parámetros ADN
- Visualización de estrategias generativas
- Simulación de crecimiento con sub-D
- Algoritmos generativos genéticos
- Técnicas de visualización
Los plugins que se verán asociados a estos conceptos son:
> Kangaroo: El plugin de Grasshopper más conocido y descargado que ya viene instalado en Grasshopper para Rhino 6. Es un motor físico que permite visualizar en tiempo real simulaciones interactivas y estrategias de form-finding.
> Galapagos: viene ya instalado con Grasshopper, es una plataforma que viene ya incluida en Grasshopper, para aplicar algoritmos evolutivos que se puede usar en situaciones y cálculos sin necesidad de conocer programación.
> Biomorpher: Muy parecido a Galapagos pero más sencillo y visual, Es un optimizador heurístico de cálculo de algoritmos evolutivos y genéticos, obteniendo la mejor solución en función de los parámetros o condiciones impuestos.
> Anemone: Usando algoritmos repetitivos, permite crear loops o estructuras secuenciales como los fractales.
También en función de la dinámica del curso se pueden ver otras apps como Weaverbird (subdivisión de mallas), Firefly, etc…
ntación en distintos procesos del Diseño. Se abordaran los conceptos basicos y la metodologia para abordar problemas de diseño a traves del desarrollo de Herramientas Algorítmicas mediante un proceso de programacion visual.
Como nuestras herramientas de trabajo se utilizara Rhinoceros+Grasshopper+Wea verBird
Instructor: Leonardo Nuevo Arenas[Complex Geometry]
Fechas: 5 y 6 de Noviembre 2011
Lugar: Sebastian Bach 5411, Col. La Estancia, Zapopan Jalisco.http://g.co/maps/nc7g6
Cupo: Limitado a 10 plazas
Costo:
Profesionistas: $3,300.00
Estudiantes: $2,800.00
Fecha limite de pago: Viernes 28 de Octubre
Importante:
Los participantes deberán traer su propia Laptop con todo el software y actualizaciones (originales o versiones de demostración oficiales) previamente instaladas. (Se fijara una fecha unos días antes para revisar que todos los equipos estén en orden y listos para trabajar). Si planeas venir de fuera de la ciudad contactanos y te pondremos en contacto con otras personas que también vayan a hacerlo para en caso de desearlo puedan compartir su lugar de estancia.
Contacto:
Complex Geometry
Leo[33 3956 9209]
[nuarle@msn.com]
FARA.Architectural Lab
Aye[33 1050 3482]
[ayeritza.fara@gmail.com]
Para hacer tu pago via deposito o transferencia electronica:
Banamex
No. Cta. 6035264
Sucursal. 0644
CLABE interbancaria: 002671064460352648
Beneficiario: Leonardo Nuevo Arenas
Al hacer el movimiento bancario favor de enviarnos el comprobante (scanner del boucher o captura de pantalla de la transferencia) a los correos de contacto que aparecen mas arriba.
http://cgeometry.blogspot.com/…
rids Surface divisions Panel creation in Rhino Panel morphing and aggregation Panel placement via attractors and colors Panel smoothing with Weaverbird Parametric panel modules TIME 3pm – GMT, London 4pm – Paris, Brussels, Rome, Vienna, Budapest, Bratislava, Warsaw 7pm – Dubai, Abu Dhabi, Baku 6:30pm – Tehran 6pm – Baghdad, Moscow, St Petersburg 5pm – Istanbul, Athens, Helsinki, Cairo, Johannesburg 1pm – Rio de Janeiro, São Paulo, Montevideo 12pm – Buenos Aires, Santiago 10am – Toronto, New York City, Bogota, Lima 9am – Mexico City 7am – Los Angeles ADVANCED SESSIONS (live) The Advanced sessions put the essential knowledge into practical use. The advanced sessions explain specific design strategies, lead you through complex Grasshopper® definitions, show tips and tricks, put plug-ins into use and show you how to connect Grasshopper® to external software and devices. MICHAEL PRYOR Designer, working in the architecture field for four years now on a variety of major built and in construction projects in NYC and China. Co-partner to 3D-Dreaming: Architecture from a digital point of view. Daily user of grasshopper: both in work and exploration, as well as a constant contributor to the grasshopper help forums. Tutor to a variety of digital design and parametric workshops hosted by the Architecture Association with [AY]A Studio, Rese arch, and 3D Dreaming. Creator of the grasshopper tutorial blog [FORMul[a]RCH]. Currently in process of writing his first grasshopper plug in. WEBINARS The rese arch Grasshopper® sessions are unique for their thorough explanation of all the features, which creates a sound foundation for your further individual development or direct use in the practice. The webinars are divided into four groups: Essential, Advanced, Iterative and Architectural. If you are a Rhinoceros 3D or Grasshopper® newcomer, you are advised to take all the Essential sessions before proceeding to the next level. If none of the proposed topics suit your needs or if you require special treatment, you can request a custom-tailored 1on1 session. All sessions are held entirely in English. The webinars are series of on-line live courses for people all over the world. The tutor broadcasts the screen of his computer along with his voice to the connected spectators who can ask questions and comment in real time. This makes webinars similar to live workshops and superior to tutorials.…
Added by Jan Pernecky at 9:39am on January 8, 2015
of computational design and a comprehensive knowledge of cutting-edge technologies in the fields of parametric architecture, robotics, digital manufacturing and 3d printing for the construction industry. The program is a part-time executive format (one week per month during one year) designed for a selected group of architects, engineers, designers and digital artists. DESIGN by DATA is made of courses, fabrication and prototyping workshops, conferences, digital talks and networking events. The program take place in multiple locations in Paris and is a true opportunity to enter the international ecosystem of architectural innovation. A coworking membership and a full fablab access to digital manufacturing machines are included in the program.
..........
PROGRAM
A) ART AND CULTURE IN THE DIGITAL TURN Digital Culture and Liquid Spaces (Yasmine Abbas)
Smart cities and Collective Intelligence (Domenico Di Siena)
Art, Technology and the Creative Process (Eric Vernhes)
Advanced Mesh Modelling and Data Bodies (Andrea Graziano)
Agent Based Tectonics for Architecture (Alessio Erioli)
B) COMPUTATIONAL DESIGN: COMPLEX GEOMETRIES AND OPTIMISATION
Management and Design of Complex Geometries (Olivier Baverel)
Conceptual Structural Design (Romain Mesnil)
Algorithmic Optimization (Cyril Douthe)
Permormance-driven Design (Sébastien Perrault)
C) ADDITIVE MANUFACTURING AND ROBOTIC FABRICATION
Robotics and Industrial Fabrication (Thibault Schwartz )
3d Printing and Material Science (Justin Dirrenberger)
Drones and Aerial Robotics for Environnemental Design and Architecture (Aldo Sollazzo)
Digital Prototyping and Final Project Fabrication (Minh Man Nguyen)
APPLY FOR SEPTEMBER 2016
http://www.enpc.fr/design-by-data…
ours looks like). Anyway, you'll probably want to start with a Fader 1-way. I set mine up to go from 0 to 300 over the course of 6 seconds. Then I just wrote a very quick C# component to check the output of the Fader component and whether it met one of three conditions. Here's the code (very simple). Note: you'll need to use the input manager to remove one of the Y input and the output manager to add 2 more outputs (B & C).
if (x <= 100) { A = true; B = false; C = false; } if (x > 100 && x <= 200) { A = false; B = true; C = false; } if (x > 200) { A = false; B = false; C = true; }
Now, we know if at any given Fader value if it's in the first phase, second phase, or third phase. I output a boolean value which can also be considered a 0 or 1 if converted to an integer. So, if I multiply those boolean values by 255, then the one that is true will be 255, and the others will always be 0. Now, you should have your color scheme which switches depending on what phase its in. Simply connect that to the Uno Write component (with the Firefly Firmata sketch loaded on your board) and send the color values to the board as PWM values.
Some things I should note... You probably notice the Fader component looks a little different (it's missing the start input and I'm using the GH_Timer). I've decided (for good reason) to abandon the Form Timer I was using in a lot of the Firefly components in favor of the newly re-written GH_Timer component. So, in order to get the Fader component to update in the next version, you have to connect a Timer and turn it on (not that much different). But, it's significantly faster. Part of the reason is that the form timer just wasn't fast enough to get really smooth results... Now, it's blazing fast. I've incorporated this Timer scheme in a lot of the Firefly components and the results are roughly 10x faster. Since, you're only switching values (and not trying to quickly modulate the PWM values) the current version of Firefly should be just fine (just use the Start input to start the Fader component). But, when we release the next version (hopefully very soon), this may change a bit. Anyway, I hope that clarifies it a bit. I've attached a screenshot below. I didn't include the file because I've got a newer version of Firefly that would just crash on you (or not open properly)... but hopefully you can get how to do it.
…
e project, considering its complexity and dimension, required a wide series of IFC files, associated to a specific database of pdf documentations. When I read about your mention “the IFC file generate by DECODE”, the only thing I can imagine is that you grabbed a single file belonging to the hierarchy and probably you didn’t really understand the structure of the whole project database. As Valerio Bonora asked, I’m curios to understand what kind of professional relationship brings together a RhinoForYou trainer with one of the companies that participated to this public procurement. If this relationship doesn’t exist, please let me suggest you to consider the legal implications that your action may produce.
Secondly, reading your phrase “may be i could remodelize all the projet, but in few month not like DECODE, with real frabication constraint, not theoric”, I believe that you have no ideas of the complexity of this project and the series of difficulties that all the participants to the PRO phase met during its development, until the delivery of the procurement documentation. During the development of the project 12 people were dedicated for 6 months just to generate the model. Do you really believe to be able to do the same work all alone in a shorter period?
Probably, as a designer, you are not confident with the phases, relationships, processes and problems which characterize the development of such complex architectural project. Honestly, I cannot understand how you can affirm to be able to cover this work package without any support.
Thirdly, under a merely logical point of view, how can you imagine to find people so proud about their results if they, as you describe, are going to present/represent a “shame”? As Mr. Bonora affirmed, construction companies appreciated the result that we proposed to them and this fact actually distinguishes our reality from your assumptions.
Finally, even if you based your evaluation on a single file of the whole database that composes the Canopée project, even if you probably used this file for purposes that differ from those it was generated for, and even if you met a single bug or a mistake into this file, let me say that your post does not represent a professional approach to reporting and/or debugging. With your negative comment you didn’t allowed us to understand and evaluate the problem, and furthermore to understand where the problems comes from: and this last information, which is still missing, represents the unstable basis of your superficial comment.
Taking distance from your action, I believe that one of the most important concepts associated to a serious and professional approach of a single member into a wider community consists into the ability to accept and/or report each other’s mistakes. Reading your post I don’t feel you as part of this concept, not at all.
Best regards,
Matteo Lo Prete, MScArch.
…
component I just used different components and GH tools to do the same - and this become part of my short paper submission for SimAUD 2016). My solution compares the height of the same points of different solar envelope and then chose the lowest one. I read about the improvement you are working on and it is good but I think it is not yet what I need (or how the solar envelope tool could be more complete).
What I need is a solar envelope that would guarantee on different facades with different orientations (the example I sent you) a certain amount of direct sunlight, say 4h per day in a given period for example all the month of June at 60°N. So to guarantee the south facing facade I should chose the vectors from 10 to 14. But these are not ok for all the other facades because in this timeframe the East and West facing facades get only 2 hours and the North get 0 hours.
So the fist step would be have the possibility to chose different sun vectors for different facades. For the example I did (the 4 hours in June at 60°N) the south facing facade would need from 10 to 14, the East facing for example from 8 to 12, the West facing facade from 12 to 16 and the North facing facade from 6 to 8 and from 18 to 20.
If I would chose a single longer time frame that could get all these hours, from 8 to 20 then the resulting solar envelope would result probably smaller than the sum of the four solar envelopes.
But this is not complete yet. I mean the use of different sun vectors on different facades. The reason is that for example when I chose the sun vectors from 8 to 12 for the four hours on the East facing facade how do I know that the sun hit on the facade in that time frame or maybe it is obstructed by surrounding buildings? Since the sun at 60°N (where I live) in June rise at around 3.15 then maybe for that specific facade the sun hit from 4 to 8 and not from 8 to 12.
I did an extreme case talking about 60°N and that maybe the sun hit on a facade at 4 instead than 12, but it is just to make understand the logic. My suggestion for a more advanced solar envelope it should be integrated with the Sunlight Hours tool of ladybug. So the input should not be the sun vectors because I don't know when the sun hit on the facade but the input should be just the desired number of hours and the possibility to specify different number of hours for each facade. Then this last component that sum different solar envelope (I didn't use it yet but I understood what it does) should be integrated yes so the result would be one single solar envelope more likely using the lowest points (the highest I don't understand what for).
Let me know what you think!
…