e técnicas avanzadas de modelación 3d y su fabricación digital (corte láser e impresión 3d). Se utilizara Rhinoceros y Grasshopper, no es necesario tener conocimiento previo de los programas, únicamente manipular algún programa CAD.
Fechas:
Miercoles 13: 18:30 a 22:30Jueves 14: 18:30 a 22:30Viernes 15: 18:30 a 22:30Sábado 16: 11:00 a 14:30 y de 15:30 a 21:00Domingo 15: 11:00 a 14:30 y de 15:30 a 21:00
Fecha límite de Pago: lunes 11 de Junio del 2012Estudiantes: $160.000Profesionales: $220.00
Descuento para integrantes de Makerspace del 40% (5 cupos únicamente)
Importante:
Todos los niveles de experiencia son bienvenidos el único requisito es tener un entendimiento básico de los programas CAD y una actitud positiva hacia el aprendizaje de dichas herramientas. Necesitas llevar una laptop, nosotros te instalamos los programas de prueba.
Si planeas venir de fuera de la ciudad avísanos 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.
Al participar en el workshop obtienes el 50 % de descuento en la licencia educacional Rhinoceros por medio de Rhino Chile.
Proceso de Inscripción:
El participante deberá pagar la matrícula haciendo un depósito bancario a la cuenta que aparece a continuación.
Banco: Estado
Nombre: Luis de la Parra Galván
No. Cuenta: 00169946655
Para obtener los datos restantes para hacer una transferencia o depósito mandar un mail a info@chidostudio.com
El depósito mínimo para reservar la matrícula es del 50% el resto deberá ser cubierto el día del evento.
Una vez que el depósito se haya llevado a cabo el participante deberá enviar a este correo info@chidostudio.com los siguientes datos:
Nombre completo
Email
Teléfono
Institución educativa u Oficina
Archivo adjunto del recibo del depósito bancario
En cuanto recibamos la información immediatamente nos pondremos en contacto para especificar los pasos a seguir.
Contacto Santiago [Sede]
Luis de la Parra
Cel: 714-660-33
info@chidostudio.com
http://www.facebook.com/Chidostudio
Todos los mails se responden en un máximo de 24 horas.
Muchas gracias por tu interés saludos…
a solve adjacencies component, it will overwrite the previous adjacencies (and constructions of those adjacencies like air walls) unless you set the "remCurrentAdjc" input to "True." I assumed that these were the zones that you wanted connected with air walls:
I set up the model to correctly simulate the zones in this fashion. There were a number of other errors that I fixed:
1) You did not intersect the building masses before you turned them into zones. This means that heat flow acorss the interior surfaces will not be modeled correctly. See this video (https://www.youtube.com/watch?v=cDvBWDA0aF0&index=10&list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_)
2) You did not set up your shade/context geometry correctly. You must use a conext shading component (https://www.youtube.com/watch?v=D7pN7nWj-4o&index=24&list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_). Also, I would highly recommend simplyifying your shade geometry. The shade calculations that E+ uses by default are not that detailed so the little gaps between your louvres are not goung to show up.
On another note, I noticed that these zones are supposed to have different programs but you have assigned them all the same zoneProgram for energy simulation. You might want to at least consider distinguishing your apartment and corridor zones. I know that it is really long but I would really recommend going through this whole series before trying to set up such a complex model:
https://www.youtube.com/playlist?list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_…
I change paramenters in GH sliders I see the progress in rhino with 4/5 seconds lag.
I think it is not an hardware issue, this is my configuration
Mainboard SuperMicro
Dual CPU Xeon x5650 (24 total core)
12GB DDRIII ECC
Hdd velociraptor 300Gb
Vga Nvidia Quadro FX3800
Hi, I attach the project files; when I move the slider bubbles trying to slide from a little value to another (like 50, 120, ecc) the result on screen is slowly to be shown.My question is, with the pc configuration listed above, is it normal with this project?There are parameters I can set in Grasshopper or Rhino to have faster results?There's a specific driver or configuration for my video card to improve performance?I would be very interested to see if the hardware on my system allows optimal performance with grasshopper or is normal with a definition so short ,even if it is the Voronoi , the system so slow to refresh when I move the slider
Thank you for your time…
lls? I am going to be laser cutting and have a bed size of 24" x 48". (It's a 12' x 12' cube, each cell is fabricated individually)
There are a few solutions I would see as acceptable but I can't figure it out:
1. Be able to see the bounding box for each cell and I can manually control the number of points and the spacing to visually check each fits in my machine.
2. Be able to actually limit the cells to the max dimensions of the bounding box and have it be an "incomplete" voronoi diagram until I have enough points properly spaced.
3. Be able to have GH determine a minimum number of points and spacing so that the square is complete and the cells fit within a bounding box (my machine bed).
Any help here would be great. Let me know if any additional information can help, and if this question has been answered too many times.…
ay how many valid permutations exist.
But allow me to guesstimate a number for 20 components (no more, no less). Here are my starting assumptions:
Let's say the average input and output parameter count of any component is 2. So we have 20 components, each with 2 inputs and 2 outputs.
There are roughly 35 types of parameter, so the odds of connecting two parameters at random that have the same type are roughly 3%. However there are many conversions defined and often you want a parameter of type A to seed a parameter of type B. So let's say that 10% of random connections are in fact valid. (This assumption ignores the obvious fact that certain parameters (number, point, vector) are far more common than others, so the odds of connecting identical types are actually much higher than 3%)
Now even when data can be shared between two parameters, that doesn't mean that hooking them up will result in a valid operation (let's ignore for the time being that the far majority of combinations that are valid are also bullshit). So let's say that even when we manage to pick two parameters that can communicate, the odds of us ending up with a valid component combo are still only 1 in 2.
We will limit ourselves to only single connections between parameters. At no point will a single parameter seed more than one recipient and at no point will any parameter have more than one source. We do allow for parameters which do not share or receive data.
So let's start by creating the total number of permutations that are possible simply by positioning all 20 components from left to right. This is important because we're not allowed to make wires go from right to left. The left most component can be any one of 20. So we have 20 possible permutations for the first one. Then for each of those we have 19 options to fill the second-left-most slot. 20×19×18×17×...×3×2×1 = 20! ~2.5×1018.
We can now start drawing wires from the output of component #1 to the inputs of any of the other components. We can choose to share no outputs, output #1, output #2 or both with any of the downstream components (19 of them, with two inputs each). That's 2×(19×2) + (19×2)×(19×2-1) ~ 1500 possible connections we can make for the outputs of the first component. The second component is very similar, but it only has 18 possible targets and some of the inputs will already have been used. So now we have 2×(18×2-1) + (18×2-1)×(18×2-1) ~1300. If we very roughly (not to mention very incorrectly, but I'm too tired to do the math properly) extrapolate to the other 18 components where the number of possible connections decreases in a similar fashion thoughout, we end up with a total number of 1500×1300×1140×1007×891×789×697×...×83×51×24×1 which is roughly 6.5×1050. However note that only 10% of these wires connect compatible parameters and only 50% of those will connect compatible components. So the number of valid connections we can make is roughly 3×1049.
All we have to do now is multiply the total number of valid connection per permutation with the total number of possible permutations; 20! × 3×1049 which comes to 7×1067 or 72 unvigintillion as Wolfram|Alpha tells me.
Impressive as these numbers sound, remember that by far the most of these permutations result in utter nonsense. Nonsense that produces a result, but not a meaningful one.
EDIT: This computation is way off, see this response for an improved estimate.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 12:06pm on March 15, 2013
but rather than keep everyone waiting, I've decided to share some as they become ready.
This also has the advantage that questions about components can be more easily grouped under the relevant post - so please do add any questions / comments / bugs / suggestions about these examples below.
So today I am posting some examples of the mesh utilities that come with the new release.
While these are not directly physics based, many of the forces and types of relaxation in Kangaroo are designed to work with meshes, and in the process of development I've ended up adding a number of simple utilities to make working with them a little easier.
I recommend also installing Weaverbird which has many more subdivision functions and other useful tools for working with meshes in Grasshopper. Also Plankton, Turtle, MeshEdit and Starling extend these possibilities still further.
Diagonalize
This component replaces every edge of a mesh with a new face. The new faces will always be quads, except for along the boundaries, where they will be triangles. It can be used to easily create diagrids. The input mesh can contain any mix of triangles and quads.
When treating the edges of a quad mesh as springs, diagonalizing it will often significantly change its physical behaviour. If you are trying to planarize a quad mesh, diagonalizing may sometimes allow you to stay closer to a target shape if it matches the curvature directions better.
diagonalize.gh
Checkerboard
This component assigns the faces of a mesh into a checkerboard pattern. The output is a list of 1s and 0s (which could represent black/white or true/false) which can be used to dispatch the faces into 2 lists, where no pair of adjacent faces have the same colour.
One nice application I found for this is applying alternating clockwise and counter-clockwise rotations as shown below. Also, on occasion you may want to planarize a quad mesh, but have some constraints on the shape and grid that prevent this, and triangulating only alternating quads to give a hybrid quad/tri mesh can sometimes be a good compromise, allowing a bit more freedom.
Note - Not all meshes can be assigned a checkerboard pattern!
As a simple example, take a mesh with 3 quads around one vertex - If we assign one black face, then both the neighbouring faces should be white, but then we have 2 white faces adjacent to one another, which violates the checkerboard condition.
Generally, we can say that if a mesh has any internal vertex with an odd number of faces around it, then we cannot apply a consistent checkerboard pattern to it (although not having any odd valence vertices is not in itself an absolute guarantee that a mesh is 'checkerboardable').
checkerboard.gh
WarpWeft
This sorts the edges of a quad mesh into 2 lists of line segments, which are like the warp and weft directions of a fabric. They can also be seen as a sort of mesh equivalent to the u and v isocurves on a NURBS surface.
This can be useful if you want to control the shape of a tension structure, because it allows you to assign different stiffnesses in the 2 directions.
As with the checkerboard component, not all meshes can be consistently assigned warp/weft directions. It follows a similar rule - all internal vertices should have an even number of adjacent faces. With a bit of care, it is usually possible to model the initial mesh in such a way as to allow this.
This component also has an output telling us whether or not each line is on a boundary of the mesh, as we will often want to treat these differently.
Same mesh relaxed with different warp/weft stiffness:
warpweft.gh
MeshCorners
This one is hopefully fairly self explanatory. In many simulations we want to anchor the corner points of a mesh. This saves us having to pick them manually in Rhino.
It works on quad meshes, and looks around the boundary vertices for any which do not have exactly 3 connected edges.
corners.gh
That's all for now. Coming soon - a "mesh tools 2" post explaining more of the components.…
nteraction in the design of an enclosed volume.
Revolutions have occurred through architectural history and vary widely in terms of design methods and fabrication techniques. Focusing on inspiring natural form‐finding techniques, AA Athens VS works towards producing a large‐scale interactive prototype that alters in real‐time the perception of interior space.
Technology and architecture are coupled for the third year in Athens with a novel agenda of transforming an enclosed area and creating internal contrasting city‐life characteristics that transcend the local conditions. In collaboration with the National Technical University of Athens, Cipher City: Revolutions explores participatory design and active engagement modeling and continues building novel prototypes upon horizontal planes.
The toolset includes mainly ‐among others‐ Rhino Grasshopper, Processing and Arduino platforms. With the completion of the Programme participants receive the AA Visiting School Certificate. In 2013, the design agenda of AA Athens will connect with the agenda of AA Greece VS in the city of Patras. Participation in both Programmes will allow for a more extensive learning experience through additional tools like Autodesk Maya, Autodesk 3D Studio Max and more.
Discounts
The AA offers several discount options for participants wishing to apply as a group or participants wishing to apply for both AA Athens and AA Greece Visiting Schools:
1. Standard application
The AA Visiting School requires a fee of £600 per participant, which includes a £60 Visiting Membership. If you are already a member, the total fee will be reduced automatically by £60 by the online payment system. Fees are non-refundable.
2. Group registration
For group applications, there will be a range of discounts depending on the number of people in the group. The discounted fee will be applied to each individual in the group.
1. 3-6 people group: £60 (AA Membership fee) + 540*0.75 = £465 (25 %)
2. 6-15 people group: £60 + 540*0.70 = £438 (30%)
3. more than 15 people group: £60 + 540*0.65 = £411 (35%)
3. Participants attending AA Greece VS and AA Athens VS | 40% discount
For people wishing to attend both AA Greece VS and AA Athens VS, a discount of 40% will be made for each participant. (The participant will pay the £60 membership fee only once.)
£60 (AA Membership fee) + (540*0.60)*2 = £708
Eligibility The workshop is open to architecture and design students and professionals worldwide.
Applications
The deadline for applications is 24 March 2014. A portfolio or CV is not required, only the online application form and payment. The online application can be reached from:
http://www.aaschool.ac.uk/STUDY/VISITING/athens
Contact:
Alexandros.Kallegias@aaschool.ac.uk…
more elaborated ways to make a definition, don't you agree? But never say never, he he.
2. Well...here's an explanation (more strange cases to follow) :
(a) Imagine 3 identical sets of data (in this case the main tube lines > truss is Modular by now, but this is user controlled). Say truss1, truss2, truss3. Structure of data is 100% correct - see, for instance - the secondary/diagonal truss items that are 100% correct.
(b) Imagine EXACTLY the same portion of code applied in the 3 sets as above (er...the "cut and paste" crude thing).
(c) It works...er...in 2 out of 3 cases > see notes (and Saved View) about where the problem is: appears that for some reason (that I can't imagine) GH fails - when working with the truss1 data, i.e 72 lines that belong to 3 branches each having 24 items - to create "properly" 3 branches of data.
(d) Data (the module connecting flanges/profiles for Loft etc etc) are collected "randomly" thus the Loft fails, the "grouping" per truss segment fails .. and in general chaos is the name of the game. But only in the truss1 case (is this an Omen of some sort?).
NOTE: Tree8 is used (but the cluster alternative fails as well, so it's not a Tree8 issue).
Compare EXACTLY the same thing working perfectly with the 2 other trusses
Morel1: Karma, what else?
Moral2: Path to glory is long (and hilly).…
for effectively designing with Grasshopper for Rhinoceros. We will cover concepts such as Object Attributes/Parameters, Data Types, Data Structures, and Designing with Algorithms. Specifically, this Webinar will focus on creating and manipulating both Lists and Data Trees as well as best practices for integrating Grasshopper into your Professional Workflow. We will leave plenty of time during the Webinar to discuss some of the more interesting updates to Grasshopper9.0.
This Webinar is Free and will last 2.5 hours including a 30 minute Q & A session. Registration can be found here:http://modelab.nu/?p=7162
Topics:
What is Parametric Design and When is it Useful? :: Fundamental Concepts and Essential Skills
What’s an Algorithm and How can I use one to Explore my Ideas? :: Defining and Executing Parametric Design Solutions
The Path to Success! How do we store and access Data? :: Working with Lists and Data Trees
Now what? Using Grasshopper in my Creative Workflow. :: File Layout, Organization, and Modularity
Details:
Instructors: Ronnie Parsons + Gil Akos | Partners, Studio Mode.
Participants: All experience levels are welcome. This webinar is Free but has limited enrollment. Reserve your seat now!
Software: Rhino 4 -or- Rhino5 Beta | Grasshopper 0.9.0006
Schedule: 1:30PM-4:00PM EST.
Examples of Previous Workshops.
This Webinar is generously sponsored by McNeel & Associates.…
el conversion tends to work unsatisfying.I tried 2 methods.
I see. Yeah, you have to be pretty specific about your vector shapes when you downscale. They must be aligned exactly with the target pixel grid, otherwise you get blurry results. I admit it's a bit of a skill that a lot of programmers can't really afford to learn. Time constraints and all that.
You are right, I might dispose the idea with the imagebox, because I still need to draw 24x24 icons then anyway. I probably will work more with Inkscape. I might also abstract it more, and probably spend more time onto good documention.
If you don't like your icons, you could always set the icon display mode of your component to NickName in the constructor. But that wouldn't help with the icons on the tabs and panels obviously, but then nothing will.
Another possible way forward (still not recommended, but that's just my opinion) is to adjust the component layout to use larger images for your components. Say 48x48, or 64x64. If that's something you'd be interested in, I can have a look at what it would take.…
Added by David Rutten at 3:09am on January 9, 2017