n. The material - lightweight fabric, weights only just about 30 kg. The only rigid structural elements, the steel rings, 3 and 4 meters in diameter form the boundaries of the shape, which is stretched between them, creating an extraordinary visual experience for the visitors.
The shape is basically a replica of original Green Void by l-a-v-a
http://www.l-a-v-a.net/projects/green-void/
The software used in design workflow: Rhino, Grasshopper, Kangaroo, 3ds Max, Lamina design.
Fair enough to say, this design would not exist without these great software giants, but special credits go to Lamina design)
http://laminadesign.com/
Author's blog: http://designcompute.tumblr.com/…
Added by Artyom Maxim at 6:09pm on January 18, 2013
ld be the best UI.
I think difference is made by 'Slider = 10' vs 'Slider = 10.000' more than by simple input/component initialization so, why to stop when it could be even more powerful?
Slider = 0 To 5 --- Slider in [0, 5]
Slider = {3; 0 To 5}
Slider = {3;0;5}
Slider = 3;0;5
Slider = 3 0:5
Slider = 3,0,5
Slider = 3 0 5 --- Value and range (min max)
3 0.0 5 --- 3.0 0.0 5.0
3 0 5.0 --- 3.0 0.0 5.0
3.0 0 5 --- 3.0 0.0 5.0
-1 0 5 --- 0 0 5 (-1 -1 5)
6 0 5 --- 5 0 5 (6 0 6)
Slider = 0:2:6 --- Even numbers: 0, 2, 4, 6.
Slider = 1:2:7 --- Odd numbers: 1, 3, 5, 7.
0:2:5 --- 0:2:4 (or 0:2:6)
3:2:8 --- 3:2:7 (or 3:2:9)
3 1:2:7 --- 1 3 5 7 (value 3)
Bang! = 7 --- 7 outputs
Merge = 5 --- 5 inputs
What's your opinion about Bang! = 7? As it's setting number of inputs, should it use different format? Bang! 7? Bang! (7)? Bang! i7?
+ * - / \ % ^ & | ! = > --- Addition, Multiplication, Subtraction, Division, Integer Division, Modulus, Power, AND, OR, NOT, Larger than, &c.
= could be a problem.
\ Integer division or Set difference?
! could be NOT but also Factorial.
| could mean intersection.
& could mean concatenate.
1+ --- Addition: input A = 1
2* --- Multiplication: input A = 2
+{0,1,1} --- Addition: input B = {0,1,1}
0-, 1/, 2^, 10^, e^ have their own components
Flatten = {7} or Flatten = 7 --- Input P = {7} (off-topic: Why can’t P be a list?)
Pt = {1, 2, 3} --- Point XYZ, X = 1, Y = 2, Z = 3.
Swatch = 129,239,231 (102)
Swatch = 129 139 231 102
F2 = "x^2+y"
"List Length" and "List Insert" don't work properly: "Value List" is choosen. Why? What's the reason to this choice? Well, I'd like to know how the whole thing (search by keywords) works, David.
Name and nickname can be now used as keywords. "Larger" works for ">" but "greater" doesn't. Could it be improved? Could synonyms be used? Could a short description even be used (I know this could be a bit weird)?
more than --- >
more or less --- Similarity
more less --- Similarity
red green --- Sets.List components should be showed
lightning --- Split Tree
What about use Curve.Analysis or Math.Boolean to display those Tab.Panel components? Param, Math, Sets, Vector? Primitive, Special, Util? Tab, Panel, and Tab.Panel as keywords.
At the moment that I write this, I check that ignoring accents in keywords has almost been included (0.8.0009): p`anel, pañel, pánel --- panel (almost)
Shouldn’t 'Dom2' work for Dom²?
What about nested search? You type some keywords (say 'Params' or 'Params.Geometry', or 'red green', or 'lst') and then you make a fine-tunning search over previous results/keywords. Tab.Panel and/or nested geometry could be useful when search by plug-in is desired or when you want to search among .ghuser components (first 'ghuser' or 'Extra.MyPlugIn' or 'lst' keyword and then fine-tunning, specific, search).
Is 'list length' performing this nested search right now ('lst' > 'length')? Anyway, I am thinking about UI (graphical) changes; successive searches.
As I said, description (and even words from the help info) could be used to search. What about "some kind of tags"? I mean that if 'list l' to finally choose List Length has been used for a while, that could be learned. Eventually, an XML file could store these tags, so you could even edit them. That could implement description, name, nickname, help info, Tab.Panel, .ghuser, synonyms (lots of them), tags/shortcuts or wathever.
How could flatten/graft/reverse be used? Initialize graft+Simplify or graft+Bang! could be really useful.
What about expressions? I don't how could it be done properly: would Slider = x^2 (expression) work? I mean, aren't expressions parsed when initializing?
Is Panel somehow doing this? 'panel = wathever' always suppose that wathever is a string, so you can't use 'panel = <pi>'. Sets.Strings components also do this.
I've been about to write several paragraphs about height/width (resizable components: Panel, Graph Mapper, Slider, &c.), input/output names (Scripts, F components; or any component with editable input/output names), orientation (Scribble), type hint and access option, nickname, &c. but, to sum up: being able to set any property when initializing would be really useful. I'd like to know the best choice of syntax but I'm sure that, David, you're closer to the answer. What do you think about this?
Slider: 3 0 5 "MySlider" "Slider^2"
Panel: "This is the content" "This is the title"
VB: "N" List Integer 7 "r" Item Double
Addition: A 1 B 2
I guess that any unified syntax would be elegant and useful, but additional ad hoc syntax (per component) could be even better (cleaner).
What about use lists of values? I'm not sure about format: panel = ("Hello", "Bonjour", "Hola")? If any valid format/syntax is found, maybe more sophisticated fetaures could be achieved: panel = {0;0} ("A", "B", "C") {0;1} ("1", "2", "3") How would you like this to be implemented?
There is a much simpler and interesting feature that would be useful, in my opinion: being able to initialize more than one component. I mean say 7xSlider = 10.0 and get 7 sliders and I also mean multiline (multi-component) initialization: Ctrl+Intro when you want to start a new line and Intro (or even some Accept/Cancel buttons when you activate multiline mode) to initialize (every line/component), for example. I mean:
3 x Slider = 1
Panel
Mass addition
Panel
And the whole bunch of components that were in mind (pre-thinked definition) is initialized. It speeds up the workflow, making more dynamic to add components that are only available via the drop-down panels.
Should this multiplier be something like a text box adjacent to search field more than '7x'?
These are some of my thoughts about intitializing. Please let me know your opinion :]
…
berfläche des Grasshopper Programms
Funktionsprinzip eines grafischen Algorithmus-Editors (Datenfluss)
Unterscheidung von Parametern (Datentypen) und Komponenten (Datenverarbeitung)
Erzeugung, Bearbeitung und Analyse von Geometrie-Typen: Punkte, Vektoren, Linien, Kurven, Flächen (surfaces, brep) und Netze (meshes)
Strukturierung der Daten anhand von Listen und Bäumen
unterschiedliche Verknüpfungsmöglichkeiten von Parametern (data matching)
praxisnahe Grundlagen der Geometrie und Vektorrechnung für generatives Design
effizienter Aufbau von parametrischen Modellen anhand Übungsaufgaben
Auszug von Daten aus Modellen für die Fertigung; Daten aus Tabellen (Excel, CSV) importieren, exportieren
Einsatz von benutzerdefinierten Komponenten (custom components)
Vorkenntnisse: Rhinoceros3d Benutzeroberfläche der Software: Englisch Unterrichtssprache: Deutsch, auf Wunsch auch Englisch
Details und Anmeldung:
www.vhs-stuttgart.de
Dieser Kurs wird in Kooperation mit ifBau gGmbH und VHS Stuttgart angeboten, und wird von ifBau als Fortbildung für Mitglieder der Architektenkammer BW anerkannt.
Trainer: Peter Mehrtens
Kursdauer: 3 Tage / 8 Stunden pro Tag
Freitag, 24.01.2014, 09:00-17:00 Uhr Samstag, 25.01.2014, 09:00-17:00 Uhr Sonntag, 26.01.2014, 09:00-17:00 Uhr Ort: VHS Stuttgart, Fritz-Elsas-Str. 46/48
Teilnahmegebühr: 510,00 € Teilnehmerzahl: 4-10 Personen
…
ino al suo utilizzo per la risoluzione di tematiche di modellazione complessa di ARCHITETTURA e DESIGN.Durante le lezioni si insegneranno i comandi avanzati del software Rhinoceros ed inoltre i discenti, alla fine del percorso formativo saranno anche in grado di creare modelli attraverso il linguaggio della Plug-in avanzata Grasshopper(http://www.grasshopper3d.com/photo).
Il workshop si divide in due moduli che possono essere frequentati anche separatamente:
STRUTTURA
mod.1 _MODELLAZIONE BASE con Rhinoceros | Venerdì 14 Dicembre e Sabato 15 Dicembre | dalle 10,00 alle 19,00
Scadenza iscrizione: Lunedì 10 Dicembre
mod.2 _MODELLAZIONE AVANZATA con Rhinoceros e Grasshopper | Domenica 16 Dicembre e Lunedì 17 Dicembre | dalle 10,00 alle 19,00
Scadenza iscrizione: Mercoledì 12 Dicembre
SINTESI
mod.1 _MODELLAZIONE BASE con Rhinoceros
L’obbiettivo del corso è quello di insegnare in tempi brevi, gli strumenti base della modellazione 2D e 3D e la renderizzazione dei modelli creati. Le ore saranno dedicate allo studio dell’interfaccia del software Rhinoceros e all’apprendimento dei comandi base per la gestione del documento di progetto; si approfondiranno i comandi più utilizzati per l’editing e la costruzione del disegno per arrivare alle operazioni booleane semplici e complesse. Inoltre si imparerà a costruire e trasformare curve e superfici free-form. Le nozioni ed i metodi verranno trasmessi trattando temi e problematiche reali di design ed architettura.
mod.2 _MODELLAZIONE AVANZATA con Rhinoceros e Grasshopper
Il secondo modulo tratterà forme complesse implementando la modellazione avanzata di Rhinoceros con le potenzialità espresse dalla plug-in Grasshopper. La plug-in di Rhinoceros permette di disegnare abbandonando l’usuale interfaccia dei software di rappresentazione, consentendo un rapporto più diretto con il linguaggio proprio del computer: la programmazione. Questo cambiamento porta ad una radicale variazione del rapporto che il progettista ha con lo strumento di rappresentazione digitale. I partecipanti saranno orientati verso un nuovo rapporto con le forme create che oltre ad essere frutto di trasformazioni delle entità primitive che Rhinoceros propone, si costruiranno anche in relazione a parametri variabili.
Nel corso si imparerà a comporre algoritmi semplici, di carattere principalmente geometrico, in grado di generare forme e gestire i comportamenti delle stesse se sottoposte a variabili esterne.
In fine si imparerà a confrontarsi con un contesto evolutivo, che influenza i parametri della rappresentazione portando a dei modelli dinamici.
…
o connect the 'Line' for ClampLength and how it relating to Lower- and UpperLimitation.
they have differently lower and upper limitation configuration between red/blue (L:10; U: 10000000) and yellow/green(L:3; H:19)...are those parameter meaning something..?
It would be nice if you could explain about that ;-)
Otherwise, awesome example!
…
Added by Jon to Kangaroo at 3:27am on May 23, 2016
NTRO 13 SETTEMBRE
Plug it2 è il primo step del percorso formativo e rappresenta l’evoluzione di Plug it, il corso più seguito in Italia sulla modellazione parametrica, giunto al quarto anno consecutivo di attivazione. Plug it2 fornirà ai partecipanti un’effettiva padronanza delle principali tecniche di modellazione tradizionali e basate su algoritmi ed approfondirà le metodologie della progettazione parametrica nel campo dell’architettura e del design del prodotto. Il corso è rivolto a studenti e professionisti con esperienza minima nel disegno CAD (acquisita su qualsiasi piattaforma software) e si articolerà in lezioni teoriche ed esercitazioni guidate. L’esperienza maturata attraverso didattica, pubblicazioni e collaborazioni professionali ci ha consentito di sviluppare un metodo efficace che non si limita al solo studio del software ma approfondisce gli argomenti teorici legati al controllo delle geometrie complesse: studio di curve e superfici NURBS, superfici matematiche, analisi di curvatura, sviluppabilità di superfici, discretizzazione.
INFO…
version on the github uses E+ 8.2. We have not yet updated Honeybee to 8.3 but I think that there is a good chance we will do this before the next stable release, which I imagine should be pretty soon.
Nite, it looks like all of the errors that you are getting with the successful simulation have to do with the specifics of your geometry so the overall E+ results on the zone level should be fairly accurate but values for individual surfaces will not be. To fix the problem, you can either accept the surface-level inaccuracies and change the solar distribution type (what Abraham suggests), you can break up all of your L-shaped surfaces into rectangular surfaces (this usually fixes everything for me), or you can break up your single zone into 3 cube-like zones with air walls between them (this always works for me).
Hope this helps,
-Chris…
0;0}, {1;1,0;0}, {2;1,0;0} .... {n;1,0;0}, {0;2,0;0}..... l
i tried to put it in a loop and copy but i get it {0;0,0;0}, {0;1,0;0}, {0;2,0;0} .... {0;n,0;0}, {1;0,0;0}, {1;1,0;0}, {1;2,0;0} .... {1;n,0;0}, {2;0,0;0}..... like #2 in image.
i tried to reorder it and got #3 but that way i have to copy it 'n' times which is not possible.
anyone can enlighten me how it can make work?
thanks in adv…
Added by deli dumrul at 2:01am on November 30, 2016