300895
FB: https://www.facebook.com/ChidoStudio
FB: https://www.facebook.com/WEDOTdesign
Detalles:
Instructores:
Arturo de La Fuente (Chido Studio Argentina)
Eliana Monaco (Chido Studio Argentina)
Luis de La Parra (Chido Studio Mexico)
WS ROSARIO
Lugar:
DOSCASAS
ROSARIO: Sarmiento 1232 Planta Alta (2000 Rosario)
Fechas:
Viernes 16 de Mayo 2014 – 11:00 – 19:00 hs
Sábado 17 de Mayo 2014 – 11:00 – 19:00 hs
Domingo 18 de Mayo 2014 – 11:00 – 19:00 hs.
WS BUENOS AIRES
Lugar:
GARAGELAB
BsAs: Roseti 1380 CABA
Fechas:
Jueves 22 de Mayo 2014 – 18:00 – 21:00 hs
Viernes 23 de Mayo 2014 – 18:00 – 21:00 hs
Sábado 24 de Mayo 2014 – 11:00 – 20:00 hs.
Domingo 25 de Mayo 2014 – 11:00 – 20:00 hs
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.
COSTOS:
Profesionales: $1600
Estudiantes: $1400
Si ya realizaste algún Workshop de Chidostudio tenes un 20% descuento en esta inscripción.
Si venis en grupo con 2 amigos más cada uno tiene un %20 de descuento.
Proceso de Inscripción:
El participante deberá un mail a bsas@chidostudio.com donde se le enviará el procedimiento y medios de pago.
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 correobsas@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:
Arturo de La Fuente
bsas@chidostudio.com
Tel: (+54) 11-57268799
…
tion plays a role, so number 1 and 7 are maybe the same in math sense but not by my definition.
but what im aiming for is plotting out all possible combination of lets say n=50 cubes. so i need some kind of logic to generate these combinations. filtering ( and predefing start combinations-like dedackelzuchts link ) out these combinations according to some criteria would be the next thing.
i have no scripting abilities therefore my question was if this could be done also by gh components.
i thought about something like this:
add cube
extrude one face (x,y or z) -> one possible geometry (if orientation doesnt play a role)
check the two cubes
extrude one face (faces that are at same position are not valid) - > two possible combinations
check the 3 cubes
...
and so on
the thig is that the combinations branches and i have no clue how to do this with grasshopper.
thanxs a bunch
…
other objects to figure out how many distinct states a slider can have and then also set one of these states.
For example imagine a slider from 1.000 to 2.000 with 3 decimal places. This slider can have a states like: 1.000, 1.001, 1.002, 1.003, ..., 1.578, 1.579, 1.580, ..., 1.999, 2.000
This adds up to one thousand and one different states, which you can find out by using the Grasshopper.Kernel.Special.GH_NumberSlider.TickCount property. There's another method that allows some remote actor to set a specific state. For example you can say GH_NumberSlider.TickValue = 50, which will set the slider to 1.049. Galapagos prefers to use integral numbers to floating point numbers, so it talks to sliders using these ticks. If however you want to set specific values, then you can use TrySetSliderValue() and SetSliderValue() and assign decimal values directly.
It's important to note that the remote object (be it Galapagos or Anemone or whatever) has to call these methods specifically. There's no way to create a 'reverse connection' with a slider and have it work automatically.
--
David Rutten
david@mcneel.com…
Added by David Rutten at 12:47pm on March 12, 2014
cs algorithms are ill-suited to calculating the transmission of a partially open screen. The sampling of rays required, and indeed the lack of actual wave-based movement of sound intensity makes them only suitable for large scale studies of spaces making the following assumptions, among others:
- The primary behavior of sound can be described by rays
- Diffraction lends only low significance effects
- Few, preferably no obstructions between the source and reciever
With regard to sound hitting a partially open screen, a variety of behaviors come into play. Sound moves in and out and around various points of a screen - meaning that rays can not describe the behavior of sound for such small delicate structures.
The good news is that some of the latest versions of Pachyderm also employ numerical methods. Try typing "Pachyderm_Numeric_Timedomain into the command prompt, and you'll get the controls for the Finite Volume Method. This method accounts for wave-based phenomena.
Now more bad news: The method does not have implemented an insertion loss calculation, so you would have to work in the source code to implement it, and it still does not have materials implemented (that last part may not be terribly important unless you intended to use porous sound absorptive materials).
So, in any case, I don't recommend using Pachyderm to determine the sound transmission of your design. Now for some more good news - you can do a rough calculation on a calculator, making a few assumptions, if you know the open area of your screen. Let's say that we assume your materials do not transmit at all (which they won't, but they will transmit far less than any opening in the screen). So let's assume you design a 50% open area screen. The transmission loss of the assembly, independent of octave band will be at most:
TL = 10*log10(0.5) = 3 dB
This means that the noise from your source will be 3 dB less on the quiet side of the screen than it will be on the railway side of the fence. Let's say that isn't enough... ok 20% open.
TL = 10*log10(0.2) = 7 dB
So now it is 7 dB less on the quiet side than it is on the rail side (it will probably be up to 3 dB louder at low frequencies, but this is a rough estimate).
So now the last bit of bad news - it is difficult, maybe impossible to get a strong amount of attenuation with a screen with open area. Even with a wall with no open area, the maximum attenuation will be 20 dBA. When you open it up, this will severely hamper the isolation of the screen. I hope this helps.
- Arthur…
ves (13 in the attached file)
2 - I shift the curve list, in order to be able to use points from one curve and the curve above simultaneously.
3 - I divide those curves on multiple points (50 points each in the attached file)
4 - This is where it gets messy: I want to access the points as follows:
Pick the items 1 and 2, then the items 3 and 4, and like that with all the points.
I've generated a series with a {0;0}(n) structure. The first branch goes from 0 to 13 (the number of curves) and the second tree goes from 0 to 25 (half the point quantity) and n = 2.
I've the curves in a {a} structure, where "a" goes from 0 to 13.
So, what I finally have is an item component, where the curves are provided as list set, and the series as the item input. So, for each curve, I have 25 pairs of item index (0,1;2,3;4,5;etc.).
I thought that the out would be all the points of the curve sorted in pairs, but I get just two points per curve, and also a lot of points in the last curve. I have tried with tree branch and tree item and I keep getting no results. Moreover, I think that item component has the ability to pick specific items in tree-structured lists, so I don't know what is happening.
I have attached a screenshot and the GH definition. In order to work, you must create a circle in rhino viewport and then reference it in GH.
I've been stucked with this for several days, so any help will be appreciated.
Thanks in advance.…
.5 (50%) will make everything look half as big, a zoom factor of 3.0 (300%) will make everything look 3 times bigger.
The code I use in the Variable Parameter tip looks like this:
Dim box As RectangleF = Attributes.Bounds Dim pt As New PointF(box.X + 0.5F * box.Width, _
box.Top + 0.5F * box.Height) Dim view As New GH_NamedView("zui_zoom", pt, _
10.0F, GH_NamedViewType.center)
view.SetToViewport(canvas, 1200)
I use a fixed zoom factor of 10.0 but you'll need to compute a variable zoom level each time. Basically, the zoom level you want it the factor you need to multiply the Attributes.Bounds with in order to make them as big as the viewport.ScreenPort So if the ScreenPort is 950 pixels wide and 720 pixels high and the Bounds of the attributes are 55 pixels wide and 75 pixels high, the zoom factor to make the width and height fit exactly would be:
Dim zoomW As Single = Convert.ToSingle(950/55)
Dim zoomH As Single = Convert.ToSingle(720/75)
Dim zoom As Single = Math.Min(zoomW, zoomH)
Where zoom is the lowest of the two. I hope my math isn't wrong, I didn't test this and only just woke up... But that's the basic idea.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 2:18am on February 16, 2012
fused now because I'd like to use brute-force instead of genetic/swarm algorithms. I am worried about fitness landscape and local extremes with my variables. On the other hand Colibri Iterator would compute millions of combinations in my case.
I'd like to use Colibri brute force+Design Explorer to explore different solutions. I am not sure how many combinations there would be but I assume that up to 10^7. That is a lot of data to compute and look through. Probably impossible to do.
I looked into 3rd example on Design Explorer page (the building one) which is pretty close to what i want to do. As far as i understand the graph, there are 9 variables. Each has different domain. My calculation for number of combinations (going from left to right - from 'elevator width' to 'solid wall amount') is 3*5*5*10*6*4*10*50. That is 72.000.000 combinations. On design explorer page there are around 250 solutions. I probably do not understand something or there is a way to filter data somehow.
My questions are - Is it even possible for Colibri Iterator to go through such huge data? Have you got any tips how to filter that data so that only chosen solutions are saved to *.csv file? Maybe I am missing something and there is another way used for design explorer examples? Any tips or tricks? :)
Thank you for your time and help,
Have a nice weekend…
s, the participants will focus on the key advantages of Grasshopper’s capabilities through a range of design challenges in order to aid designers in both their drafting tasks and modelling capabilities.
The workshop covers many concepts such as Object Attributes/Parameters, Data Types, Data Structures, and Designing with Algorithms. Specifically, this course will focus on understanding both Lists and Data Trees, as well as the best practices for integrating Grasshopper into your Professional Design Workflow. The workshop offers guided curriculum and continuous support, based on in-depth and professional learning experiences.
Workshop outcomes:Teach the participants how to:-
+ be proficient in parametric logics learning the key benefits of parametric techniques in architecture design workflow (when to use it & how to use it)+ Correctly communicate with different 3D and BIM packages in order to keep the geometry clean and light while preserving all NURBS information.+ Develop architecture design based on mathematical equations to create non-standard free form building skin.+ Create a pattern that changes dynamically based on specific inputs which can be applied over the building façade, interior walls or ceiling or even floor pattern.+ Automate and Optimize design variables to achieve the optimum solution for the design problem.
Program Outline:
DAY 1:-Introduction to Parametric Design -Introduction to Grasshopper & Rhino (technical tools).
DAY 2:-Exploring the parametric workflow. -Setup the design algorithm & generating a list of data.
DAY 3:-Introducing the new ways of generating parametric curves and surfaces.-Parametric form generation in-dept
DAY 4:-Introducing Data Tree logic and parametric transformations.-Creating Associative techniques – Attractors (points, curves and vectors).
DAY 5:-Working with advanced form generation with dynamic pattern.-Parametric optimization based on environmental analysis -featuring the Performance-Driven Design possibilities
DURATION:6 – 8 hours per day [50 - 60 hours Total]Every Saturday [9.00 Am : 1.00 Pm & 2.30 Pm : 6.00 Pm]
PREREQUISITES:No need of any specific knowledge of Rhinoceros or Grasshopper.
REGISTRATION:In order to register, you will need to fill the Registration Form .https://docs.google.com/forms/d/1PckdW1hrWs9fJAHWBZlVsuhH8K0PfDuMWIpXHT_4FYw/viewform
REGISTRATION DEADLINE:23th October 2014.…
Added by ayman wagdy at 7:48am on October 19, 2014
g energy use of electric lighting dimming system.
But I found a major mistake in my previous test file, that is, the "lighting Power" used in the daylight simulation and the E+ simulation are NOT equal by my carelessness. The former was 250w (default value in "Honeybee_Lighting control Recipe") while the later was 11.8403571*50=592.018w (lightingDensityPerArea*Areaoffloor=lightingpower).
Having corrected this mistake (by using 592.018w for both of them), the results of electric lighting energy obtained from daylight and E+ simulations are much closer with each other and more reasonable. In order to see how close they are, I made 3 tests using 3 different weather files (New York, Amsterdam, Guangzhou). The results are listed as follows respectively:
New York (3.4% difference)
Amsterdam (2.7% difference)
Guangzhou (3% difference)
It seems that the difference (around 3%) is acceptable?
You are right. Having checked the IDF file created, as you mentioned above, there is no data in the Daylighting class (since the daylight control are not implemented in the E+ simulation). But, the light is "fully/partially" on according to the "fractions" in the generated lighting schedule list, which already takes in account the dimming system by the setting in "Honeybee_Lighting control Recipe" in daylight simulation.
Then, what the E+ simulation did in terms of calculating electric lighting energy use is just as the following formulation: lightingDensityPerArea * Areaoffloor * sum of lighting schedule list (generated by daylight simulation in this case) = electric lighting energy use, which has been verified by the comparison of results obtained from E+ simulation and calculated by the above formulation. (The results are exactly the same.) Please see the updated gh file attached.
Therefore, I assume that the E+ results generated in this way (using the lighting schedule generated by the daylight simulation) are still reliable, although there exist some tiny difference (around 3%) for some unknown reason (Maybe Daysim does not follow the same formulation mentioned above? Can you imagine the possible reason?).
In addition,
- I am not clear with what you mentioned as "they definitely don't share daylight considerations". What "daylight considerations" here refer to? (sky condition / sky file? but in the annual Daylight Simulation, only weather file is required instead of sky file)
- A basic question: In E+ simulation, has the waste heat generated by the electric lighting been considered as "internal heat gain" (showed in the above image)? If so, can I say that "energy use for electrical light" is fully converted to "the waste heat" + "Illuminance in lux".
Namely, energy use for electrical light = the waste heat + Illuminance in lux (lux can be converted to electric power in watts)?
Many thanks!
Best,
Ding…
Loft is connecting circles on her\his arbitrary way, not counting the wireframe wich is made from Crvs from points.
Like a wireframe in a picture with a last def. from you, such exact Surface I need. Maybe some sweep rail, where a every 2 circles are Rail and a arc (trough 3 point) or segment of interCrv is a section Curves.
At the endeffekt I want to accomplished a worm like a nest, something like a worm city, where people will live in a worms , to create microclima inside ( In direction of B. Fullers dome), it term that one ring(segment) of each worm is a place for 50 or more habitants. Prox. Pro worm 250-500 habitants.
My steps are:
To make a Srf’s from accomplished wireframe.
Then evaluate this surface with Ecotect (that is why I am still using GH 0.6 because of Uto’s plugin for 0.6 and 0.7). And I also have a Rhino 0.4 Sr6
Make a sun reacting facade or pneumocells.
Make a def. to assign a GH def. on multiply Crv’s. For this I need also evaluate a Crv’s length, because of subdivisions number. If I assign the same divisions number to all Crv’s , the longest and the shortest will be divided at same div. Num.! What we don’t see in a nature.
Make a living space inside of worm, with vertical farming, residents, parks etc.... Dividing a worm Srf’s on separated rings (segments) , to count their area. Bigger ring will have a more people and so on...
Make a model :)
I hope that I don’t sound too much pretentious :)…