s para resolver problemas que hoy se presentan en el diseño y fabricación digital de formas complejas, que en conjunto, son las tendencias e instrucciones mas utilizadas por las oficinas de arquitectura del mundo.
Tomando como plataforma Rhinoceros de McNeel Associates, se optimiza el diseño y fabricación usando Grasshopper, RhinoNest y RhinoCAM.
Se realizará en Lima, Perú el 12 y 13 Setiembre, de 8:00 AM a 6:00 PM., con un total de 16 horas.
Cupo máximo: 20 alumnos.
Inversión. (no incluye impuestos)
S/.900.00 Incluye Licencia Rhino
S/.750.00 NO incluye Licencia Rhino
Ambas incluyen certificado de McNeel Miami.
Instructor:
Andres Gonzalez, CEO McNeel Miami, desarrollador desde 1980. www.rhino3d.com
Organización
McNeel Miami, Pablo C. Herrera,
Pedro Arteaga y MGP Nuevas Artes www.mgp-peru.com
Contacto en Lima, Perú
Claudia Aller / contacto@mgp-peru.com
Contacto en Miami, USA
Jackie Nasser / jackie@mcneel.com…
Since I haven't had a chance to thoroughly test the Leonardo out just yet... I can tell that there are probably going to need to be a few minor changes (and potentially a few big changes). The minor changes will probably need to address the fact that a sketch doesn't 'reset' itself upon opening a serial port. This means that anything in the setup() function wont be initialized, and the serial communication might not work properly. It doesn't look like it's too hard to fix (just by adding a new while loop to check if the serial stream is open or not). But, this needs to be added to the Firmata. Some of the potentially bigger changes will deal with the fact that all 20 pins can be used for digital input and output. In addition, some of the digital pins can also be used for analog input (bringing the total analog inputs up to 12 using the Leonardo). This could potentially be really useful, especially if you could simply click on a pin in Grasshopper and tell it if you want it to be used as an analog or digital input. However, this opens up a lot of challenging tasks. Since the code would already be loaded onto the board, it would need to be able to respond to dynamic pin changes (which at the moment doesn't really happen, except for the different states for digital, PWM, and servo outputs... but in general those are all still outputs). I need to think a bit about the best way to approach this problem. Any suggestions would be greatly appreciated.
In general, I think the Leonardo can be used very similar to older boards. So, I think you could still use it with the current version of the Firmata... although I haven't had a chance to test it... and as I said, I may need to add a few lines of code just to get the serial connection established upon opening the port. I'll try to give this a look over the next week and provide some feedback. As always your input is appreciated.
Cheers,
Andy…
and diffuse radiation for 365 days at noon (12:30)
As you can see there are some bumps that I have discarded as dependant of geometry (Did simulations with different geometries even with just an horizontal surface to analyse and nothing else.) Also discarded from the solar position since the bumps happen in different days as you may see in the graph. I have also tested it with Diva and honeybee so I guess it has to be with RADIANCE. I got this data reading the illuminance files from an annual daylight simulation.
I guess it has something to be with how RADIANCE transform radiation to luminance (luminance = (RED*.263 + GREEN*.655 + BLUE*.082) * 179) And how it determines the values Red, green and blue of the spectrum for a determined solar radiation. I guess, because I was unable to learn how RADIANCE calculates this spectrum, that it has to be dependant of the radiation and solar position with a quite large difference of spectrum.
Normally this bumps are hiden behing the variation of radiation over the year, and I guess that the tool was not designed to have such unrealistic constant radiation, but I would like to know why this happens.
Can anyone help? Any clue is welcome!
Thank you.
…
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…
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
set.
The general idea being:
Create a collection of characters that enumerate your source collection. In this case the characters 0, 1 and 2 because you have 3 source words (cat, dog and tree).
Using the CharPool component you generate all possible permutations (39 in this case). These permutations start with {0}, {1}, {2}, {0,0}, {0,1}, {0,2}, {1,0}, ... and end in ..., {2,2,0}, {2,2,1},{2,2,2}
Create valid sets from these permutations, meaning any number which appears more than once will be removed. Ie. {0,1,0} becomes {0,1}, while {2,2,2} becomes {2}, while {2,0,1} remains {2,0,1}.
Sort all permutation groups. This will allow us to detect that {2,0,1}, {0,1,2} and {0,2,1} are all in fact the same thing.
Glue the individual characters in each set back into strings again, so {0;1} becomes "01" and {1,2} becomes "12".
Create a new set from all the glued together permutation groups. This once again removes duplicates.
We now have the answer we were looking for, just not in the form we can use. We need to peel apart the strings again into individual characters and then use those characters are indices into our collection of source words.
…
Added by David Rutten at 10:36am on December 13, 2016
NURBS using Rhinoceros. Content includes: Basic terminology, user interface, workflow strategies, using reference material and creating drawings from modeled geometry.
Workshop 2: Introduction to Parametric Design
Instructor: Rajaa Issa
(12:30 PM-3:30 PM)
This workshop will introduce the general framework of parametric thinking with a series of hands-on tutorials using Grasshopper for Rhinoceros. It is meant for beginners who have little to no idea about parametric modeling. The workshop will introduce the general components of an algorithm, design workflow, Grasshopper interface and visualization techniques. The students are expected to have basic knowledge of the Rhino modeling environment. Workshop 1 should fulfill this requirement.
Registration: Computers and software will be provided. Space is limited to 20 seats per workshop. The fee for each workshop is $60 (plus a $4.29 fee). There is a special rate of $30 (plus a $2.64 fee) for students and teachers provided they request a discount here with their school email address before registering. Register now……
e openings with the simple calculation of room air and IES.
I am testing a shoebox of 15x5m, 3m height, 2 windows of 1sqm, only 1 person of internal gains, no heating, no cooling, basically nothing.
The tests were running fine with the "Wind pressure coefficient type" as Input on the AFN simulation control. But, as the number of ach that I was obtaining was tiny (approx. 1/6 of the ach of room air) I thought that the problem could be the Input and my wind pressure coefficient calculations. Therefore, I changed the WPCoefficient type to "Average surface calculation" and I deleted all the wind pressure elements.
As soon as I change this (and only this) the simulation crashes because of the error "DualSetPointWithDeadBand: Unanticipated combination of heating and cooling loads - report to EnergyPlus Development Team" And also, my heating set point changes from -100 degrees to 12
I've look for this in the bigladder manual for energy plus and looks like if I had set a thermostatic zone control on dual set point with dead band, what I haven't, because, to be honest, I didn't even know it existed.
I hope any of you can help me, because I've been trying hard, but I don't find which is the problem.
I have to say that all the AFN data is internalised (beside the run simulation) and will be a bit difficult to read. I'm sorry for this but, as they are about 20 user objects, I thought it was too much to upload.
Thanks a lot…