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
…
hope u know how can i open these file :(
thanks 4 the attachment i think this will work with me but the scale is different so at the end not same size >> then i have to extrude it as Jissi Choi did .
____
Jissi Choi
can i extrude each group of triangles(which i choose ) with spsifc hight ?
so at the end i will have 3 different hight?
thaaaanks all 4 ur help i will download it all and i'll be back ..
:)
…
Added by architecture at 5:00am on December 20, 2011
ndfloor as groundfloor?
2. As I posted somewhere else this morning, here again: What's the right procedure to save E+materials into an *.idf so that created and (from library) chosen materials appear after HB's flying? Floors and Ceilings don't get E+materials from library...
3. I don't get heating- and cooling loads out of my model. Can it be that point 1. is the reason for that?
All I'm talking about in the attached file is pinky.
Attached you find the E+ Sim-Report and the *.gh file.
T h a n k y o u very much in advance!
Daniel…
hing not acceptable. To build up the final results I tried to summarize some steps and script them but I got stuck.
1) Voronoi subdivision
2) Voronoi vertices connected to the center
3) Tween curves between center and boundary
4) Control of U and V parameters
Point 4 is really important because it will allow me to control the strength of the springs in the two directions in kangaroo. Voronoi curve is going to be an anchor and the point is going to pull the mesh.
…
ility of possible (but also functional) plans in some simple module plan or better module volume (if it s could work for example also for duplex apartments or for privet houses with more than one floor). I could also image to split the module on the different parts (rooms) and let them and their position dictate the form of different modules.
And last but not the least i would like to create some generator to put those simple modules in clever and variable settlements.
as shorter conclusion.
1. floor generator in fixed form (in this case rooms should change there potions and proportions but follow some rules about for example lighting, visibility, connection between the rooms and mb min and max sizes for each function area.)
2. floor generator with fixed function areas (rooms) (in this case the plan contour or volume varieties have to be created from different arrangment from the rooms. I would lake to take care in this case of the space syntax but also lighting.
3. settlement generator which could organised different masterplans from those simple living modules.
I just started with it with research and reading of different PHd works and scripts about those themes. It s looks to be really hard.And i am kind of beginner in grasshopper and have only 3 months time. So i would be very happy for any advice, example definitions e t c.
…
s because the geometry is too big for cuting in laser machine plotter, so I Want to separate this 5 segments, If you see the image 2.
I select the item number 3 that is in the midle and its all fine, but if u watch the image 3 when i select the Item 2 for example tooks segments for randomly :(.
Its like the curves are not in the same direction, i tried to flip them but no results, I tested the curve direction and it seems all ok. Look at this:
This is killing me T_T... any commentaries...…
r more details: workshop information
The 2012 Workshops:
1. "ALGORITHMS & MATHEMATICS" - Leader: Edmund Harris with David Celento, Brian Lockyear (Rhinoscript + Grasshopper / McNeel) 2. "ROBOTIC FABRICATION" - Leaders: Proto and Kruysman (SCI-Arch Staubli Robot + Maya, Autodesk) 3. "CASE STUDIES IN PARAMETRIC DESIGN" - Leader: Andrew Kudless with and Andrew Heumann (NBBJ) (Grasshopper) 4. "ROBOTIC PROTOTYPES" - Leaders: Shiloh, DeLeon, Johnson (Arduino + Grasshopper + Firefly) 5. "COMPUTATIONAL DESIGN STRATEGIES WITH DESIGNSCRIPT" - Leader: Robert Aish with Fisher, Tierney (DesignScript / Autodesk) 6. "PYTHON SCRIPTING WITH REVIT / VASARI" - Leader: Nathan Miller (Python + Revit + Vasari / Autodesk) 7. "GIS DRIVEN PARAMETRIC DESIGN" - Leaders: Sandoval, Faichney, de Monchaux (Grasshopper, Finches, LocalCode, GIS)
About ACADIA 2012
The conference will highlight experimental research and projects that explore the reciprocity and synergy between bits and atoms, the digital and the physical, and between digital code and material logic. The conference will bring together designers, researchers and practitioners who engage, question and aspire to stretch these boundaries. Architects, fabricators, engineers, media artists, technologists, hackers and others in related fields of inquiry are invited to participate.…
tion for dividing the surface evenly in both directions:
Again, the definition is quite simple:
"A" shows standard uv-isocurves division, the result indicates that we're dealing with quite a nasty surface - the domain is very unevenly distributed.
"B" shows my solution for the same surface (copy), which consist of these steps:
1. retreive one set of iso-curves (u or v, you can toggle which)
2. divide each of them into equal segments
3. use the resulting division points to form new pseudo-iso-curves
4. divide those curves into equal segments
The result is quite nice, but there's one downside to it:
It varies depending on the starting set of curves you choose (u or v) - use the toggle button to see the difference, especially for really unevenly distributed parameter spaces.
The reason why this happens is that steps 2-4 listed above are just the first iteration of the formula. If we repeat the process several times, we should get basicaly the same result starting with "u" and "v".
With the use of receivers copying the iterating part of the definition is really simple:
Of course making iterating definitions in Grasshopper is a total nonsense, it was just a quick way to check my idea.
One thing you've got to bear in mind is that I'm no math expert and this solution is based just on a hinch and intuition... so It's possible that it would jump into a stable state (if scripted) or something...
If you like my solution and you don't come up with one which doesn't requiere iterations, you can always post a message on the VB and C corner, maybe someone could code it for you.
Ok, I think that's enough for today, I've pretty much exhausted the subject on my end :)
Let me know how the definition works for you.
Cheers,
JJ
--
as for the akward curves when using different step size and count: it's no big deal, those are just the curves which fall outside the surface domain. remember that the input parameter N in the series component is inverted (expression is: 1/N)…
yramid, the length of the sides of the base are A and B and the height is H and corner to top point lines are 'pipes', like you mentioned:
In the current system, the relation of X to one of the base sides is a 5X multiplier (not exactly, but something like that) and to pyramid height is a (3-X)+0,3 multiplier (where 3 and 0,3 are also other variables).
HOWEVER, if you want to keep the pipe length fixed for the pyramids, the correlation between the base and height is a constant, which is (if I didn't calculate it wrong) (A^2+B^2)/H. THIS IS TRUE AS LONG AS EACH PYRAMID IS SYMMETRICAL ALONG U AND V. If they are not, which is your case, I don't think that the pyramids can fold along a single line altogether without altering the pipe size.
So, to keep the pipe length fixed, one solution maybe to create symmetrical pyramids and align them parallel to the movement axis while also creating the base/height relation. That's my two cents...
extra note: By symmetrical, I don't mean a square pyramid. It can have any rectangular base as long as the apex is somewhere along the base center normal. …
lying surface + (b) trimming "info" (where to chop > and create the "boundary"). Trimming info is "grouped" in 2 things: Outer loop and inner loop(s) - the holes if they exist.
2. Thus if you evaluate a surface you'll get results with regard the surface that MAY "extend" well beyond a given visible "boundary" (in some cases with a rather weird way). Programmatically we test a given u/v coordinate for inclusion on a given Brep Face in order to find IF the face contains the point in question.
So whilst a "piece of code" like Surface.PointAt(u.v) exists ... there's no such thing with regard a Brep Face.
3. If you connect a Surface component to any BrepFace collection this gets the underlying Surface instead of the BrepFace. Try connection a Brep component (Note: a Brep can have one face the so called sheet body in several solid modelling CAD aps).
I have a C# that does (for fun) a convincing demo on all that freaky stuff ... but it's solely code.…