393&xg_source=activity
In this case we see a geometrically approach, which doesn’t works efficient, because it required knowing how they behaviors together before, and I think it is not the ‘really behaves’.
To make the structure ‘really behaves’ I tried use kangaroo and the result works very well! As you can see I simply give the 2-set reverse UForce, and then they start to rotate until they found their equilibrium. That means 90 degree rotation. I was wondering what we can do to make a endless-rotation. I am mean 360 degree or more like this:
https://www.youtube.com/watch?v=4owFczeqqMQ
By the way, I try to give supports which allow a horizontal movement only (Just curious how we could keep the anchor-movement horizontally and in the same layer, for example like usual supports for compression ring…). I use the AnchorXYZ, but Kangaroo-Engine seems don’t accept its output.
So maybe some one knows a better solution?
…
Added by Jon to Kangaroo at 7:40am on March 11, 2014
problem later) to fit more shapes that are otherwise won't fit in.
On the example below horizontal rectangle couldn't fit in but its rotated analog could and thus was placed in.
Later, when placed shapes are used to generate frames, because of this rotation, the position of the starting points changes and because of the approach I use to generate the frames some angle values are attached to the wrong corners, this brakes the frame shape and looks like this (on the left the frame of sick shape and on the right the frame of the healthy shape):
Again, this happens because the angle values are assigned to the specific corners (points) and previously rotated shapes get these all messed up:
Easy fix, don't rotate the shapes, problem is, I've already baked a good number of them for later use. I'd like to avoid regeneration because it takes a lot of time and without rotation I constrict the algorithm even more.
Better fix, use a different approach, this is where I'd like to hear suggestions and kicks in a right direction. Please take a look at my definition. It works but I have a feeling like giving an amputee a job of sweeping the floor.
…
ns. but first allow me to explain what i'm trying to do: i have a serial device i want to talk to, but i have to do it using some sort of handshaking. for instance, when i send a command/data, i need to wait for an appropriate response before sending another. i have used andy payne's general serial components from firefly, but i don't think they'll work for what i want to do, and in general, i want to know how to do this from scratch. i'm using the pyserial library to do the comm, and i can get it to work within one script. here's an example of a working (mostly) port open/close script (x=input param for baud, y=input param for port name, z=boolean input param for open/close):
import serialmyPort=serial.Serial()myPort.baudrate = xmyPort.port = yif z == True: try: myPort.open() except: print "Something went wrong. Cannot open port." if myPort.isOpen() == True: print myPort.name + " is open" if z != True: try: myPort.close() except: print "Something went wrong. Cannot close port." if myPort.isOpen != True: print myPort.name + " is closed"
this all works well and good. here are my questions:
1) I can open the port and then close it. however, if i try to re-open it, i get an access denied error. it seems rhino is holding the port open, as i have to re-start rhino to get it working again. i read through the discussions and didn't see any definitive answers to this problem. any advice?
2) I'd like to share this port with other components (or at least break up the functions of opening/closing the port and read/write, not unlike how the firefly components are organized), but i have no idea how to share an object instance between components. i did see that there is a sticky dict and tried to add myPort to it, but i kept getting errors in the other component when i try to use the object's methods. for instance:
Component 1 Script:
import serial
import scriptcontext
myPort=serial.Serial("COM4", 9600)
scriptcontext.sticky['myPort']=myPort
Component 2 Script:
import serial
import scriptcontext
myPort=scriptcontext.sticky['myPort']
print myPort.read()
but i get messages like:
Runtime error (MissingMemberException): 'Serial' object has no attribute '_port_handle'
any assistance would be greatly appreciated!!
best,
~BB~…
lla progettazione parametrica e le tecniche di modellazione algoritmica per la generazione di forme complesse
___________________________________________________________________________________
luogo:
Sala meeting Holiday Inn Inn Turin C.so Francia Piazza Massaua 21 – TORINO
Scadenza iscrizioni: 25 Novembre 2011 – ore 15.00
___________________________________________________________________________________
info e prenotazioni:
Le Penseur (coordinamento formazione)
info@lepenseur.it
081 564 21 84
347 548 71 78
quote di partecipazione e programma (formato PDF)
ulteriori informazioni sui corsi PLUG > IT
___________________________________________________________________________________
PROGRAMMA DEL CORSO:
GIORNO_01 | 01 Dicembre 2011
10.00 – 10.30: presentazione workshop
10.30 – 11.30: introduzione alla progettazione parametrica: teoria, esempi, casi studio
11.30 – 13.00: Grasshopper: concetti base, logica algoritmica, interfaccia grafica
13.00 – 14.00: break
14.00 – 16.00: nozioni fondamentali: componenti, connessioni, data flow
16.00 – 18.00: esercitazione
GIORNO_02 | 02 Dicembre 2011
10.00 – 12.00: funzioni matematiche e logiche, serie, gestione dei dati
12.00 – 13.00: analisi e definizione di curve e superfici
13.00 – 14.00: break
14.00 – 16.00: analisi e definizione di curve e superfici
16.00 – 18.00: definizione di griglie e pattern
GIORNO_03 | 03 Dicembre 2011
10.00 – 12.00: trasformazioni geometriche, paneling
12.00 – 13.00: image sampler
13.00 – 14.00: break
14.00 – 18.00: data tree: gestione di dati complessi
GIORNO_04 | 04 Dicembre 2011
10.00 – 12.00: digital fabrication: teoria ed esempi
12.00 – 13.00: nesting: scomposizione di oggetti tridimensionali in sezioni e posizionamento su piani di taglio per macchine a controllo numerico CNC
13.00 – 14.00: break
14.00 – 18.00: esercitazione…
Profesor de Proyectos Francisco Arqués Soler, experto en la materia; Una vez exploradas y programadas las decisiones generativas del proyecto, el grupo servirá de laboratorio para investigar mutaciones del mismo.
http://dpa-etsam.com/iam/iam-cursos
https://www.facebook.com/iamadridETSAM?fref=ts
Trabajaremos en la plataforma de programación visual Grasshopper, reventaremos los principios de su estructura (mediante Millipede , exploraremos las condiciones bioclimáticas (mediante Ladybug+Honeybeey navegaremos por procesos de form finding y variaciones generativas (mediante Galapagos y Octopus y su conversión a BIM (mediante Chamaleon, Lyrebird, Visualarq, puesto que el dia final programaremos la salida del prototipo a Revit).
NOTA: el curso tendra lugar la segunda mitad de este OCTUBRE, aunque el CALENDARIO aun esta abierto de manera asamblearia al maravilloso grupo reducido de elegidos que se apunten al final, aunque suele ser MARTES Y JUEVES, DE 16:00 A 18:00 HORAS.
Título Oficial de Experto en Programacion Visual por la UPM, y los creditos respectivos (en este caso 2,5)
iAM | Instituto de Arquitectura de Madrid <iamadrid.arquitectura@upm.es> +34 91 336 6537 / 6589…
een them to be adiabatic (at first. See later on for an alternative).
The whole process is fine/clear up to the solveAdjacencies: The walls are defined as "outdoors" and "surface" for the boundary conditions. So far so good.
Now i get to the HB_makeAdiabaticByType, and some issues appear (See A in the file).
Setting the interiorWalls to True doesn't change the condition from"surface" to "adiabatic" (A1 in file).
Setting the walls set both internal and external, to adiabatic (A2 in file). Is this supposed to work like this? Why the just the internal doesn't make the change?
In addition to this i'll appreciate your advice in the following. Let's say that i want the internal walls to be divided in 2 parts each. One should be adiabatic and the other "air wall". How do you recommend to do this? Is the modeling in the file correct, or i must do surface by surface?Or using the Decompose Honeybee Zone ...?
How can i retain the air walls and still use the makeAdiabaticByType component?
Thanks for your help!!
-A.
…
start (if there is a better one I would appreciate a hint), but I thought I populate a rectangle with points, interconnect the points to later let the borders of the rectangle attract each other.
I have 4 rectangles: A, B, C and D.
On each I have 20 points (A0-A19, B0-19, etc.)
Now I want to connect each point to all the points on the other rectangles, e.g. point A0 with all the (60) points on rectangle B, C, D.
I saw the discussions about the topic sorting lists (e.g. flipping), but I didn't see them fitting on this problem, or I don't know how to abstract them for me.
Also this is a problem I am having with another definition, so if someone could help me with that list stuff, I think I could use it furthermore.
But if there is a better solution to the rectangle organisation (tessellation), I am open for that.
regards,
Max
sry for the long text…
ion technologies offer a completely new way to think and approach design, architecture and urban planning.
. . .
The ADVANCED ARCHITECTURE SUMMER SCHOOL organised in Paris by VOLUMES coworking, NOUMENA architecture and architect/teacher/designer Francesco Cingolani in partnership with the prestigious École Nationale des Ponts et Chaussées is a 3 weeks learning experience designed as an immersive journey in social innovation, computational design, digital fabrication and collaborative culture.
Details and informations for applicants> volumesparis.org/summerschool2015…
r).
http://www.agrob-buchtal.de/en/cd/produkte/produkte_seiten_13045.ht...
2. 1 puts some "modular Z" increment puzzles (for more than obvious reasons). Additionally the excavation cost VS any ECO-benefits ... (heat exchangers in the foundation blah blah). OK that means that the footprint it's also modular., not to mention the whole composition (potentially).
3. So: use the projection ONLY for defining where a given footprint meets the terrain (see the yellow and blue things in V2) and then LOFT pairs (see PlanA, B) of profiles into 2 DISTINCT portions ("solids" so to speak): (a) the basement (or at least something where some potential partitions could being classified as "underground" spaces), (b) the classic building.
4. By doing 3 ... keep an eye on 2 as well (Don't forget the classic minor terrain "adjustments" around each building (meaning usage or "tmp" solids), access roads/pavements (ditto), potential connection of basements (parking), soil stabilization issues, bad seismic behavior on unevenly(Z) formed basements etc etc).…