e matching with a dedicated component which creates combinations of items. You can find the [Cross Reference] component in the Sets.List panel.
When Grasshopper iterates over lists of items, it will match the first item in list A with the first item in list B. Then the second item in list A with the second item in list B and so on and so forth. Sometimes however you want all items in list A to combine with all items in list B, the [Cross Reference] component allows you to do this.
Here we have two input lists {A,B,C} and {X,Y,Z}. Normally Grasshopper would iterate over these lists and only consider the combinations {A,X}, {B,Y} and {C,Z}. There are however six more combinations that are not typically considered, to wit: {A,Y}, {A,Z}, {B,X}, {B,Z}, {C,X} and {C,Y}. As you can see the output of the [Cross Reference] component is such that all nine permutations are indeed present.
We can denote the behaviour of data cross referencing using a table. The rows represent the first list of items, the columns the second. If we create all possible permutations, the table will have a dot in every single cell, as every cell represents a unique combination of two source list indices:
Sometimes however you don't want all possible permutations. Sometimes you wish to exclude certain areas because they would result in meaningless or invalid computations. A common exclusion principle is to ignore all cells that are on the diagonal of the table. The image above shows a 'holistic' matching, whereas the 'diagonal' option (available from the [Cross Reference] component menu) has gaps for {0,0}, {1,1}, {2,2} and {3,3}:
If we apply this to our {A,B,C}, {X,Y,Z} example, we should expect to not see the combinations for {A,X}, {B,Y} and {C,Z}:
The rule that is applied to 'diagonal' matching is: "Skip all permutations where all items have the same list index". 'Coincident' matching is the same as 'diagonal' matching in the case of two input lists which is why I won't show an example of it here (since we are only dealing with 2-list examples), but the rule is subtly different: "Skip all permutations where any two items have the same list index".
The four remaining matching algorithms are all variations on the same theme. 'Lower triangle' matching applies the rule: "Skip all permutations where the index of an item is less than the index of the item in the next list", resulting in an empty triangle but with items on the diagonal.
'Lower triangle (strict)' matching goes one step further and also eliminates the items on the diagonal:
'Upper Triangle' and 'Upper Triangle (strict)' are mirror images of the previous two algorithms, resulting in empty triangles on the other side of the diagonal line:
…
ake a modest notice about the two new Ladybug components, one of which creates a 3d terrain shading mask and another one which visualizes and exports horizon angles. A terrain shading mask is essentially a diagram which maps the silhouette of the surrounding terrain (hills, valleys, mountains, tree tops...) around the chosen location, and account for the shading losses from the terrain. It can be used as a context_ input in mountainous or higher latitude regions for any kind of sun related analysis: sunlight hours analysis, solar radiation analysis, view analysis, photovoltaics/solar water heating sunpath shading...
My home town is an example of the shading caused by the terrain. Here is how it looks from the tallest building in the town:
And the created terrain shading mask:
A mask for any land location up to 60 degrees North can be created:
There will also be a support for a few major cities above this limit.
Both Terrain shading mask and Horizon angles components can be downloaded from here. An example .gh file can be found in here.
Component will prompt the user to download and copy certain files in order to be able to run.
It was created with assistance from Dr. Bojan Savric. Support on various issues was further given by: Dr. Graham Dawson, Dr. Alec Bennett, Dr. Ulrich Deuschle, Andrew T. Young, LiMinlu, Jonathan de Ferranti, Michal Migurski, Christopher Crosby, Even Rouault, Tamas Szekeres, Izabela Spasic, Mostapha Sadeghipour Roudsari, Dragan Milenkovic, Chen Weiqing, Menno Deij-van Rijswijk and gis.stackexchange.com community.
I hope somebody might find the components useful.…
a partire dall’ap- proccio algoritmico-digitale per l’architettura, il paesaggio, la città, il prodotto, che sviluppa processi di progettazione in modo simile e vicino alle forme naturali ed ecologiche. La progettazione parametrica permette di avvicinarsi al progetto ar- chitettonico, paesaggistico, al design di prodotto, con elementi che conferiscono al processo e al prodotto finali armonia, fluidità, dinamismo, vicini ai parametri della natura, dunque molto più ecologici. L’uso della modellazione parametrica-digitale è diventato uno strumento essenziale nella maggioranza dei progetti orientati ad una pratica in cui le risposte progettuali, le invenzioni digitali e le loro implicazioni sono considerate ad un alto livello e prossime alle forme organico/naturali- ecologi- che. Per fare alcuni esempi, Zaha Hadid architects, KPF, Foster, HOK, aeDas e arup, Foa, Plasma e altri ancora sono studi internazionali di progettazione in cui l’uso della modellazione parametrica è diventata essenziale e rende riconoscibile il loro lavoro.
quota di iscrizione
Comprensiva della versione valutativa di Rhinoceros + Grasshopper e di buffet per il giorno 31 maggio _ 100 euro
note
scadenza iscrizioni: 25 maggio 2012 | ore 12.00
Durante il workshop verranno presentate esperienze di architetti internazionali che lavorano con il design parametrico. I partecipanti dovranno essere muniti del proprio computer portatile. Non è necessario possedere conoscenze di Rhinoceros o programmazione.
per informazioni e programma completo:
www.greentrendesign.it…
metrico: 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.Il metodo utilizzato prevede lo studio di diversi esercizi tematici che offrono lo spunto per affrontare alcuni temi fondamentali della modellazione parametrica. Si tratta di esercitazioni guidate in cui lo studente non seguirà passivamente una serie di procedure ma indagherà il significato dei diversi parametri e componenti che concorrono alla definizione dell’algoritmo.Il corso ha una durata di 16 ore programmate nell'arco di 2 giornate con i seguenti orari:
il giorno 08/09/2012 dalle 10,00 alle 19,00 ed i giorno 09/09/2012 dalle 10,00 alle 19,00. Le due giornate saranno intervallate da un’ora di pausa pranzo.
SCADENZA PREISCRIZIONE: 07/09…
h Shading--DC to AC derate Factor--Photovoltaics Module, can calculate the ACenergy of different pv arrays by Galapagos. The process can evaluate the self shading from the input analysisGeometry and surrounding shading from the input context.
2. PV SWH Systemsize, can also do that, but there would be no second type of self shading for the chosen minimalSpacingPeriod_ criteria.
3. TOF outputs optimal angle and azimuth.
So my question is, if I choose to make a curved roof to form a best pv array with best ACenergy, whether should I only choose the first above, the second PV SWH Systemsize can only deal with the angled or flat surface, not the curved? What's the relationship between TOF and PV SWH Systemsize?
Also, I'll do my best to make a parametric model as soon as possible and upload it to you, so we can make the discussion more detailed.
Best regards.…
face, the larger the number of modules and system size, there for the higher annual energy generation.baseSurface_ - this input exists only for "PV SWH system size" component. It's purpose is to represent a mounting plane on which the PV modules will be put onto. The dark blue colored roof in the photo below is that mounting surface in this case:
So the size of area of the baseSurface_ is not important but its plane.
2) It is important. It basically sets the initial losses of the system.
If that is the soiling value you have, then yes, you need to add it to the DC to AC derate factor component, and then plug its output to "DCtoACderateFactor_" input. I did that in the attached definition below.
3) The north vector/numeric value is not propagated due to possible independent usage of components.I plugged the 0 value to all three component's which have "north_" input. You can change it to what ever value you need.
Please let me know if I didn't answer completely to your questions, or if you have more of them.…
s complete.
Thanks for your clarification on solving derivatives geometrically. I feel like I should have been able to see that intuitively. My understanding of Calculus is based on HS Calculus taken almost 20 years ago so needless to say much of my math skills are rusted over, but I usually understand the concepts well enough to figure out what is going on, although perhaps not well enough to know where to go next. I've been wading through this problem for some time and had to learn all of the differential geometry concepts and terminology from scratch trying to piece things together. What took me weeks to figure out I was able to clearly explain to someone else in five minutes. I am determined to solve this problem and I believe I am very close to using GH to do it. An AD component still seems like an easier way to get there. =P
Thanks for your help.…
ecce adesso mi spiazza.
Dovresti cercare per favore di spiegare con immagini, e magari un file passo-a-passo? O un video?
Ho provato il tuo file, e se eseguo il comando (da riga di comando):
_Rectangle _Vertical
questo segue la direzione arbitraria del CPlane corrente e crea il tuo rettangolo. E' questo ciò a cui stavi pensado?
PS: il file funziona qui con Grasshopper 0.8.66. Hai provato a fare click con il pulsante destro e selezionare "Salva oggetto come..."?
Grazie,
- Giulio _______________
giulio@mcneel.com…
similar to any other surface in your model. Just model the shadings as surfaces and then assign either translucent material or transparent material (glass) to them and connect them to runDaylight with other Honeybee objects. Is that make sense?
Make sure to use appropriate numbers for -ab, -ad and -aa. Check page 27 of Daysim tutorial for a an example for parameters (https://dl.dropboxusercontent.com/u/16228160/Daysim3.0.Tutorial.pdf). I should add that the numbers are slightly high in the example though. Here is another reference if you want to know more about RAD parameters: http://www.radiance-online.org/community/workshops/2011-berkeley-ca/presentations/day1/JM_AmbientCalculation.pdf
Mostapha
…
f i explain how i might be able to use something like this.
i want to use the (grid)lines, and engrave them into wood on a laze cutter/engraver.
for that propos i just need a grid in lines of a checkerboard / chessboard.
I have made a chessboard design in rhino before, but I wanted to know if I could automate a part of it.(seeing that a chess board is nothing but squeres).
I will ad in the chess bord that I drew by hand (took me a lot of time).
the main part beeing the red squeres (zoom in). in evry squere there is a other squere to make the lines thinker when lazer engraving them. (i know i could just adjust the with, but dooing it this way actuely saves machining time).
…