ation production and consumption that represent our physical world in numbers and complex networks. The advent of computational systems has not only helped in developing data production but also in transmitting data between different disciplines including architecture through fields of numbers/codes. Historically, numbers and proportions played a vital role in architectural production, now; the complex flow of data is opening unexpected territories for architects. Data Flow is an advanced computational design workshop that focuses on capturing, processing and utilizing real time data from the surrounding environment by means of physical computing and parametric design tools, enabling the participants to develop informed design solutions that adapt to the environment. The workshop knowledge objective is to reconsider abstract data as a design opportunity by developing the quantitative flow of data as a qualitative design approach. /// Application To apply, please follow this link to fill the application form https://docs.google.com/forms/d/1xzKn-cZzfvu24ktTNP1ElGBAufdryfLNCXvpheucrS8/viewform /// Fees* 1700 EGP for students / 2000 EGP for graduates and young professionals * 20 % discount for early registration and payment before 22 nd of August 2014 more info on the workshop webpage: http://www.encodestudio.net/#!dataflow/cslb…
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…
10 from the other list and insert/splice them into the original list (at the specified index, not appended to the list end) while overwriting the values contained therein- how would I go about this task? Ideally, I could then, in a second step, take yet another range of indices (20, 22.. whatever) from another list and splice them in again.
Any thoughts?
Thanks & g'nite
Max…
ndomly select a list of 16 points, a list of 22 points and a list of 4 points which would then represent the three separate sized squares. Can anyone help? Much appreciated for your time.…
t the sum of the three parts equals the length of the original list). This will generate a tree of lists. If you want these lists to actually have separate outputs, you can either [Explode] the tree, or you need to use other kinds of components.
For example you could use [Split List] twice, once to split the lists into parts A&B vs. C, and then another Split List component to split the still combined A&B into separate A and B lists.
Or perhaps use three individual [Sub List] components, all with different domains that represent your desired list lengths. So using your numbers, the first splitting domain would be from 0 to 21 (for a total of 22 points), your second splitting domain would go from 22 to 25 (giving you the next 4 items) and the third domain would go from 26 to 41 (giving you the last 16 values).…
onent are experiential or location specific. For example: humidex has been derived and widely used in Canada.Also both humidex and discomfort index should be used in in-shade conditions.For universal applications and locations, you should concentrate on either PET or UTCI (this is what "Outdoor Comfort Calculator" component is based on).
I have found out, that for instance - OutdoorComfortCalculator - which considers temperatures of 9-26 and other factors, gives the % of comfortable time outdoor for instance in Kenya in Africa (high temperatures and humidity) 55%, whereas within the same .epw data and some additional factors added to the Thermal Indices component, the "humidex" or "Discomfort index" give a result drastically lower, I think it was even 1-5% comfortable.How is that?
Yes, this is one of the issues that I have with UTCI index: the authors wanted to make it as an index applicable in any type of climate. To create the UTCI comfort categories a number of data has been collected from different locations (for hot humid climate, it was the data from Madagascar. I may be wrong on this). This resulted in universal comfortable range of 9 to 26 C which you mentioned. How would the people in Madagascar perceive the feel like temperature of 9 degrees as comfortable is beyond my understanding.Thermophysiology of a human in Madagascar, and in Poland is the same. However their acclimatization is quite different, which raises the issue with the upper universal comfortable range. In general people who live in hotter climates have a bit higher tolerance to high temperature than those living in continental climates. And vice-versa: their tolerance to lower temperatures is lower than the tolerance of the people from the continental climates. Here is a comparison of the UTCI - PET stress categories:
UTCI
all climates stress category
above +46 extreme heat stress+38 to +46 very strong heat stress+32 to +38 strong heat stress+26 to +32 moderate heat stress+9 to +26 no thermal stress+9 to 0 slight cold stress0 to -13 moderate cold stress-13 to -27 strong cold stress-27 to -40 very strong cold stressbelow -40 extreme cold stress
PET
(sub)tropical humid climate temperate climate stress categoryabove +42 above +41 extreme heat stress+38 to +42 +35 to +41 strong heat stress+34 to +38 +29 to +35 moderate heat stress+30 to +34 +23 to +29 slight heat stress+26 to +30 +18 to +23 no thermal stress+22 to +26 +13 to +18 slight cold stress+18 to +22 +8 to +13 moderate cold stress+14 to +18 +4 to +8 strong cold stressbelow +14 below +4 extreme cold stress
I attached below an example of PET humid climate comparison with UTCI, for in-shade and out-shade conditions.As it can be seen UTCI shows the percent of time comfortable: two times higher than PET.
Thank you Pin, for the useful comment, on usage of "Analysis period" component.…
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…