hours/day (40 hours) Future University in Egypt (FUE) Department of Continuing Education(DCE) ________________________________________ The aim of this workshop is to teach participants how to create a parametric housing model which can be associated with day lighting and thermal analysis. Moreover, participant will get the opportunity to develop passively design envelope. The workshop is highly interactive giving different examples that develop a strong understanding of Grasshopper Workflow & different passive strategies using the performance simulation tool (DIVA). The participants are divided into groups to study the different orientations and the final outcomes of each group are presented thus concluding the recommendation strategies for each orientation. At the end of the workshop, each participant will receive a Certificate of Attendance from Future University in Egypt. Target Participants: ‐Professional architects. ‐Master and PhD students. ‐ Last year of undergraduate students (ONLY). Prerequisite: -None, however, a basic Grasshopper & Rhinoceros knowledge is preferred. Used Software:(will be provided by the instructor). ‐Rhino 5 SR 3 ‐Grasshopper 0.90066 ‐DIVA Version 2.1.0.3 ________________________________________ Workshop Outline: 1st DAY (Wednesday 29 Jan): 1.Introduction to passive design strategies (efficient envelope) 2.Introduction to parametric design logic 2nd DAY (Thursday 30 Jan) : 1.Developing technical tools based on reverse engineering technology. 2.Examples for parametric facade design 3rd DAY (Saturday 1 Feb): 1.Enforcing the parametric logics with Grasshopper 2.Introducing the performance simulation tool (DIVA) 4th DAY (Sunday 2 Feb): 1.Facade design using grasshopper ‐Studio work. 2.Associative techniques – Day lighting and thermal simulation 5th DAY (Monday 3 Feb): 1.Final optimization and final results 2.Group work presentation ________________________________________ Participants are required to bring their own laptops. To register: 1.Fill in the application form found in this link: https://docs.google.com/forms/d/18OrcwwDks5-vd0irZITC430bjMVb8I8pdw0i5OefyMg/viewform 2.Kindly pay the workshop fees at FUE DCE Admission or in the Bank account Number of participants is a minimum of 20 and a maximum of 24 ________________________________________ Workshop Trainers: Ayman Wagdy Mohamed Ibrahim Researcher at Sustainable Design research group | AUC Lecturer at Parametric design | AUC M.Sc. Architecture – Architecture and Building Technology| Politecnico Di Milano Haitham Salah Ali Mahmoud Teaching Assistant of Design course | AASTMT Head of design team | YBA Architect Principal and cofounder | Arkan Architect ________________________________________ For any questions or info please do not hesitate to contact us at : Mob. : 01003220017 - 01008551772 Email : Fue_ppd@outlook.com…
Added by ayman wagdy at 12:12pm on January 17, 2014
ceros.
Public concerné /
Architectes et designers, utilisateurs de Rhino souhaitant paramétrer Rhinocéros à l’aide de Grasshopper, programme
associant des composants et une structure de graphe interagissants avec le modèle Rhino.
Une bonne connaissance de Rhinocéros est nécessaire. La langue de la formation est le français.
Structure et Objectif de la formation /
La formation se déroule sur 3 jours : les 2 premières journées sont consacrées aux « fondamentaux » de Grasshopper
avec en préambule une introduction au design et à l’architecture paramétrique et leurs impacts dans la conception, la
création et la construction.
La troisième journée sous forme d’atelier est dédiée à l’étude de cas concrets proposés par les stagiaires, qui, quelques
jours avant la formation, pourront envoyer leurs projets par mail à info AT rhinoforyou DOT com
Les stagiaires, après la formation, pourront rester en contact avec les formateurs de HDA par le biais du blog
complexitys.com et le twitter @HDA_Paris. La durée de cette formation permettra d’atteindre une autonomie et une
bonne compréhension basée sur des exemples concrets.
3 Formules possibles /
3 jours ( Initiation+Atelier ) : du lundi 20 septembre au mercredi 22 septembre
2 jours ( Initiation ) : lundi 20 et mardi 21 septembre
1 jour ( Atelier ) : mercredi 22 septembre
Programme ind icatif des notions traitéES pendan t la formation /
Introduction à la conception Paramétrique . Rhinoscript, Grasshopper: différences et similarités . Interface
graphique de Grasshopper . Objets, Données, Listes . Opérateurs scalaires : La mathématique de
Grasshopper . Gestions des données : la logique de Grasshopper . Vecteurs, Points, Lignes, Surfaces : La
géométrie de Grasshopper . Listes, Arbres, Branches . Le dessin paramétrique: exercices divers et exemples
. Références, Bibliographie, Support de cours . Ateliers d’architecture et design paramétrique (3ème jour) .
Moda lité de la formation /
Venir avec un PC portable équipé de Rhinocéros version 4.0 SR 7 et de la dernière version du plug-in
Grasshopper (téléchargeable sur www.grasshopper3d.com).
Le coût du stage est de 350 € HT/jour par personne.
Réserver votre place dès que possible car les places sont limitées à 10 participants maximum.
Inscriptions et renseignements: Jacques Hababou, info AT rhinoforyou DOT com
Pour en savoir plus sur l’architecture paramétrique: www.complexitys.com…
2_Radiation.gh template, reorganized it a bit for a June 21 7am-7pm study (everything in orange bubbles below)… However I realized that the template was only the Sky Dome Visualization tool.
So I took a wild guess and I grabbed the Ladybug_Radiation_Analysis component using it to produce a mesh on the floor of an office building. (everything in white bubble below)
1) Is this the correct component to give me relative values of sunshade behavior? (Later I’ll connect my sunshade geometry into the Context input to block incoming daylight)
2) Is it incorrect to let the grid size be anything except 1m square? (I ask because the individual, total and average Radiation result output values swing wildly when I change the grid size.)
My Best,
Rob…
ay how many valid permutations exist.
But allow me to guesstimate a number for 20 components (no more, no less). Here are my starting assumptions:
Let's say the average input and output parameter count of any component is 2. So we have 20 components, each with 2 inputs and 2 outputs.
There are roughly 35 types of parameter, so the odds of connecting two parameters at random that have the same type are roughly 3%. However there are many conversions defined and often you want a parameter of type A to seed a parameter of type B. So let's say that 10% of random connections are in fact valid. (This assumption ignores the obvious fact that certain parameters (number, point, vector) are far more common than others, so the odds of connecting identical types are actually much higher than 3%)
Now even when data can be shared between two parameters, that doesn't mean that hooking them up will result in a valid operation (let's ignore for the time being that the far majority of combinations that are valid are also bullshit). So let's say that even when we manage to pick two parameters that can communicate, the odds of us ending up with a valid component combo are still only 1 in 2.
We will limit ourselves to only single connections between parameters. At no point will a single parameter seed more than one recipient and at no point will any parameter have more than one source. We do allow for parameters which do not share or receive data.
So let's start by creating the total number of permutations that are possible simply by positioning all 20 components from left to right. This is important because we're not allowed to make wires go from right to left. The left most component can be any one of 20. So we have 20 possible permutations for the first one. Then for each of those we have 19 options to fill the second-left-most slot. 20×19×18×17×...×3×2×1 = 20! ~2.5×1018.
We can now start drawing wires from the output of component #1 to the inputs of any of the other components. We can choose to share no outputs, output #1, output #2 or both with any of the downstream components (19 of them, with two inputs each). That's 2×(19×2) + (19×2)×(19×2-1) ~ 1500 possible connections we can make for the outputs of the first component. The second component is very similar, but it only has 18 possible targets and some of the inputs will already have been used. So now we have 2×(18×2-1) + (18×2-1)×(18×2-1) ~1300. If we very roughly (not to mention very incorrectly, but I'm too tired to do the math properly) extrapolate to the other 18 components where the number of possible connections decreases in a similar fashion thoughout, we end up with a total number of 1500×1300×1140×1007×891×789×697×...×83×51×24×1 which is roughly 6.5×1050. However note that only 10% of these wires connect compatible parameters and only 50% of those will connect compatible components. So the number of valid connections we can make is roughly 3×1049.
All we have to do now is multiply the total number of valid connection per permutation with the total number of possible permutations; 20! × 3×1049 which comes to 7×1067 or 72 unvigintillion as Wolfram|Alpha tells me.
Impressive as these numbers sound, remember that by far the most of these permutations result in utter nonsense. Nonsense that produces a result, but not a meaningful one.
EDIT: This computation is way off, see this response for an improved estimate.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 12:06pm on March 15, 2013
with Istanbul Technical University, will continue to rediscover verticality through novel generative design techniques and large-scale physical prototypes. Abstracted as a fusion of various sub-systems, each subsystem of the tower will be investigated in relation to their various performance criteria. The correlations between the separate sets of performance criteria and evaluation methods will be analyzed, leading to the generation of unified design alternatives for a vertical system typology. In addition to the custom-made digital design and evaluation tools supporting the core methodology, Vertical Interventions will also highlight the fabrication and assembly of a large scale working prototype integrating the performative characteristics of each system in examination.
As in 2012, the design agendas of AA Athens and AA Istanbul Visiting Schools will directly create feedback on one another, allowing participation in either one or both Programmes.
Discounts
The AA offers several discount options for participants wishing to apply as a group or participants wishing to apply for both AA Istanbul and AA Athens Visiting Schools:
1. Standard application
The AA Visiting School requires a fee of £695 per participant, which includes a £60 Visiting Membership. If you are already a member, the total fee will be reduced automatically by £60 by the online payment system. Fees are non refundable.
2. Group registration
For group applications, there will be a range of discounts depending on the number of people in the group. The discounted fee will be applied to each individual in the group.
Type A. 3-6 people group: £60 (AA Membership fee) + 635*0.75 = £536.25 (25 %) Type B. 6-15 people group: £60 + 635*0.70 = £504.5 (30%) Type C. more than 15 people group: £60 + 635*0.65 = £472.75 (35%)
3. Participants attending both AA Istanbul and AA Athens | 40% discount
For people wishing to attend both AA Istanbul 2013 and AA Athens 2013, a discount of 40% will be made for each participant. (The participant will pay the £60 membership fee only once.)
£60 (AA Membership fee) + (635*0.60)*2 = £822
For more information in discounts, please visit:
http://ai.aaschool.ac.uk/istanbul/portfolio/discounts-2013/
Applications
The deadline for applications is 21 March 2013. A portfolio or CV is not required, only the online application form and payment. The online application can be reached from:
http://www.aaschool.ac.uk/STUDY/VISITING/istanbul…
Added by elif erdine at 11:41am on December 13, 2012
t strange because when I ran the same model in Archsim switching off the Airflow Network mode and working on Simple Ventilation (for wind and buoyancy) it took around 2 minutes only to run the simulation for a single day. I don’t understand why the big difference in time since both plugins use Energy Plus?
- Do you happen to know why Airflow network simulation produce quite different results (temperature and ach) from those obtained from Simple Ventilation (both in Archsim)?
- I agree that I do not need the Air flow Network now, since at this phase I am trying to optimize the form of the double façade (folds, opening sizes, depth, etc.) to get a balance between temperature, airflow, and daylighting needs in the office rooms. I really think heat gain, airflow, daylight (thermal and visual comfort) all influence each other and if possible should be studied together while designing building skins. The plan was to do this using Galapagos, but I am not so sure now given the long simulation time (adding to it daylight simulation too). Anyway, in a later phase I wanted to know how the airflow in the office rooms would be like…as I understand, that could not be done yet in HB right? that’s why I thought of the Airflow network in Archsim.
- Thanks for reassuring that the double façade could be treated as a single zone. I am adjusting the model now as you said..that first trial was just to know if it works. I’ll probably use custom openings as some of them will be glazed (on some of the triangular faces, and sizes will depend on incident solar radiation on each face) while others are small air openings (on the mullions and the top horizontal face) to ventilate the cavity and avoid overheating. Also when external air temperature is within comfort range, it could be used for ventilation he office spaces.
- About CFD in design builder, i double checked again on their website when u mentioned it, and found the report comparing Design Builder’s results to Pheonics: https://edmshk.files.wordpress.com/2014/08/designbuildercfdvalidationvsphoenics.pdf
However I am not sure if this is considered and official validation, and weather it would be valid for complex geometry, not just a room in the form of a cube as in the report. Anyway I don’t think it will work out for me as I tried exporting a gbxml and when I opened it in DesignBuilder it does not understand that this is a zone…also all openings (which I added later to the file) were not exported. I tried exporting your parents' house since I’ve been working on your tutorials (great videos by the way! So much help!) and when I opened it in Design builder, not all rooms were understood as zones (especially the attic). So that rules out DB for me I guess.. I downloaded OpenFoam but turns out to be quite a challenge to use. Lots of learning awaits me!
Sorry for my long reply, and thank you for your help!…
roposes now) definition is not quite right as stated above. From this link (sorry for that, but i'm lazy to look for a better one) we can see that:
The terms sky component and sky factor refer to the actual contribution of the sky to daylight, after considering both luminous distribution and incidence angle effects. There appear to be no hard and fast rules as to the type of sky distribution to be used with either term, however they are typically calculated using either the CIE Uniform Sky or CIE Overcast Sky to remove the dynamic effects of beam solar component.
After that the definition of VSc, as given by the BRE:
The Vertical Sky Component (VSC) is described by the UK Building Research Establishment (BRE) as the ratio of the direct sky illuminance falling on the vertical wall at a reference point, to the simultaneous horizontal illuminance under an unobstructed sky [Littlefair, 1991]. It also states that the Standard CIE Overcast Sky model is to be used for the sky illuminance distribution. This means that the reference value for the VSC percentage is effectively the unobstructed horizontal sky component.
And that's why i like a bit less the definition above (just sky component) and then generalizing the concept for all other possible surfaces.
As for SVF, doing a quick search of recent (relatively) sources that are trying to develop methodologies to define SVF they are based almost exclusively on solid/geometrical considerations. See these references for illustration:
Grimmond C.S.B., Potter S.K., Zutter H.N. and Souch C. 2001. Rapid Methods to Estimate Sky-View Factors Applied to Urban Areas. International Journal of Climatology. 21: 903–913 (2001). DOI: 10.1002/joc.659
Matuschek, O. Matzarakis, A. 2010. Estimation of Sky View Factor in Complex Environment as a Tool for Applied Climatological Studies. In: Matzarakis, A., Mayer, H., Chmielewski, F.-M. (Eds.), Proceedings of the 7th Conference on Biometeorology. Ber. Meteorol. Inst. Univ. Freiburg No. 20, 535-540.
Matzarakis A., Matuschek O. 2011. Sky view factor as a Parameter in Applied Climatology - Rapid Estimation by the Skyhelios Model. Meteorologische Zeitschrift, Vol. 20, No. 1, 039-045 (Open Access Article).
Hämmerle M., Gál T., UngerJ. & Matzarakis A. 2011. Comparison of Models Calculating the Sky View Factor Used for Urban Climate Investigations. Theoretical and Applied Climatology (2011) 105:521–527. DOI 10.1007/s00704-011-0402-3.
I know some other researches that use the term SVF just from its geometrical implications. This is probably because all those are based on site measurements or photographing.
It will be really interesting to calibrate those with the new LB component.
Thanks again,
-A.…
would require to use archsim in grasshopper but it seems to be giving me a ton of errors. Some negligible but others are quite adamant.
Anyone know how to use archsim and is willing to help out? I've attached the 3dm and gh, I've been pulling my hair out for the past three days figuring everything out!
SCHOOLS.3dm
SCHOOLS.gh
If need be, I'll gladly talk to anyone who can help me with my current predicament. This is the error i get on one of the buildings
1. Program Version,EnergyPlus, Version 8.2.0-0ba4142206, YMD=2015.10.25 21:32,IDD_Version 8.2.0
** Warning ** CheckUsedConstructions: There are 1 nominally unused constructions in input. ** ~~~ ** Each Unused construction is shown. ************* Construction=DEFAULTCONSTRUCTION_FLIPPED ** Warning ** GetPurchasedAir: ZoneHVAC:IdealLoadsAirSystem="UNNAMEDZONE_0 IDEAL LOADS AIR missing data ** ~~~ ** UNNAMEDZONE_0_OUTDOORINLET does not appear in an OutdoorAir:NodeList or as an OutdoorAir:Node. ** ~~~ ** Adding OutdoorAir:Node=UNNAMEDZONE_0_OUTDOORINLET ************* Testing Individual Branch Integrity ************* All Branches passed integrity testing ************* Testing Individual Supply Air Path Integrity ************* All Supply Air Paths passed integrity testing ************* Testing Individual Return Air Path Integrity ************* All Return Air Paths passed integrity testing ************* No node connection errors were found. ************* Beginning Simulation ************* Simulation Error Summary ************* ** Warning ** The following schedule names are "Unused Schedules". These schedules are in the idf ** ~~~ ** file but are never obtained by the simulation and therefore are NOT used. ************* Schedule:Year or Schedule:Compact or Schedule:File or Schedule:Constant=OFF ** Warning ** The following week schedule names are "Unused Schedules". These schedules are in the idf ** ~~~ ** file but are never obtained by the simulation and therefore are NOT used. ************* Schedule:Week:Daily or Schedule:Week:Compact=OFF_wk_ ** Warning ** The following day schedule names are "Unused Schedules". These schedules are in the idf ** ~~~ ** file but are never obtained by the simulation and therefore are NOT used. ************* Schedule:Day:Hourly or Schedule:Day:Interval or Schedule:Day:List=OFF_dy_ ************* ************* ===== Final Error Summary ===== ************* The following error categories occurred. Consider correcting or noting. ************* Nominally Unused Constructions ************* ..The nominally unused constructions warning is provided to alert you to potential conditions that can cause ************* ..extra time during simulation. Each construction is calculated by the algorithm indicated in the HeatBalanceAlgorithm ************* ..object. You may remove the constructions indicated (when you use the DisplayExtraWarnings option). ************* ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors. ************* EnergyPlus Completed Successfully-- 5 Warning; 0 Severe Errors; Elapsed Time=00hr 00min 5.00sec
Let me know if you can help!
Kind regards,
Kevin…