ectural project, the efficiency of design communication and the control of information-flow are as important as the creativity of ideas. In response to the concurrent digital evolution emerging in the architectural industry world-wide, the Faculty of Architecture at The University of Hong Kong will host a two week intensive summer program named Digital Practice.Led by professors from The University of Hong Kong, as well as invited practitioners with expertise in practice of cutting edge digital techniques, the program offers participants opportunities to experience applications of computational tools during different stages of an architectural project, i.e. concept design, form finding and optimization, delivery, management and communication of design information under the team-based working environment. By learning advanced computational techniques through case studies in the context of Hong Kong, participants are expected to go beyond the conventional perception of technology, considering users and tools as a feedback-based entity instead of a dichotomy. The program, which is taught in English, includes a series of evening lectures related delivered by teaching staff and invited local architects.對於高品質的建築專案,創意之外,專案過程中高效的設計資訊管理和交流成為項目設計深化和實施必不可少的環節。今天,數字化技術不但改變了建築師的繪圖工具,影響了設計的過程,而且提供了工程建造和管理實施的更有效、更高效的手段。針對建築的數位化演進,香港大學建築學院將於2011年暑假期間,在香港大學建築學院舉辦“數位化實踐”國際研習班。在香港大學建築學院教授及有著相關豐富經驗的外聘實踐建築師的指導下,學員將有機會體驗在專案的不同階段(如概念設計、設計形式的生成、優化,設計資訊的管理和交流),如何有效地應用各種運算智慧化技術(從設計的數位化生成和建築資訊類比到物理模型),提升設計實施的品質,增加設計團隊對於方案的控制。我們將挑戰對於“技術”的傳統認知,即相對於使用者它不僅是工具,更是與使用者互動的媒介,二者形成一個有機的合體。研習班期間會安排系列講座,展現數位化技術在實踐工程中的廣泛應用。…
Lets say I supply the Rectangular Grid Component with 3 different planes (and Sx, Sy, Ex, Ey have some single, fixed, values...lets say 4x5 grid). What I would like to have as an output is an array of 3 Rectangular Grids. Therefore, if I add 10 new planes, I would like to see 10 more Rectangular Grids. But the problem is I get an array of all the rectangles in all of the Grids together...so instead of 3 Grids, I get an array of 60 rectangles. If I add 10 new planes, Ill get another 200 rectangles.
How do I make it so that I dont have to think about what happens after the Rectangular Grid Component? When I add more planes I would like the same operations be performed on them without changing anything after the Rectangular Grid.
P.S. When I try to extract a branch I get a bundles with "columns" - 5 rectangles....this doesnt help much...for every new plane I get new "columns" I have to deal with additionally...
Thanks!…
selname with rhinocommand.
Curently your scipt exports 200 item for 10 min.
I have over 3,000 item per file and I have 5 files.
For all elements with a rough calculation it makes:
(15 000/20)=750 min (it's so long)
Thanks for all
…
che di modellazione algoritmica per la generazione di forme complesse. Il corso è rivolto a studenti e professionisti con esperienza minima nella modellazione 3D e si articolerà in lezioni teoriche, esercitazioni e sviluppo di un progetto finale.
tutor: Arturo Tedeschi - autore di "Progettazione Parametrica", il primo manuale italiano su Grasshopper
lecturer: Davide Del Giudice | Zaha Hadid Architects | Co-De -iT
guest: Maurizio Arturo Degni
assistant: Matteo Gobbi
info e programma:
http://www.comese.me.it
…
ed to study it carefully to understand grafting, simplifying, etc. Any recommended data structure/tree tutorials?
Optimization works very well, even with as few as 200 sample points. This is the result of about 5 minutes of evolution.…
nderstand each other quite well.
I will pick one piece of the PVsurface at the bottom row:
So the label "1" represents the PVsurface for which the shading diagram will be created.
Label "2" is the back facade (made of glass or opaque elements, does not matter).Label "3" represents the row of PVsurfaces above.
Now take a look at how the shading diagram would look like for the mentioned PVsurface. I made some of its parts a bit incorrect on purpose, so that I could clearly the differences a bit easier:
Label "1" would be first type of self-shading. It's the shading which prevents the PVsurface to "see" anything behind its back.Label "2" would be shading from the facade wall to which the PV surfaces are attached to. I deliberately colored it blue, to distinguish it from other two types of the shading. Otherwise it would look black.Label "3" is the second type of self-shading: the shading from the above row of PV surfaces.In literature, you won't find the terms: first and second type of self-shading. I invented them.To my knowledge, when self-shading is mention, this will probably be related with label "3" (second type of self-shading). It's the shading from the adjacent rows of PV modules in front, or like in this case above.So when I said:
You do not have to supply the surfaces additionally to the context_ input. The component will "under the hood" add them to the context_ input to account for self shading. Last year this hasn't been the case, but after the suggestion by Chris Mackey, I changed this feature.
This was related to the first type of self shading (label "1").
And when I said:
However, as we are using the PV SWH System size component, there will be no self-shading. The PV SWH System size component positions the PV rows in such a way, that no self shading will appear for the given minimalSpacingPeriod_ criteria.
This was related to the second type of self shading (label "3").
I should also mention that I made the upper photo a bit incorrect. If you would do the shading analysis, the label "3" would be almost non-existent. Here is how the shading diagram would actually look like:
As mentioned this is because PV SWH System size component will position each PVsurface row in such a way, so that there would be no second type of self shading for the chosen minimalSpacingPeriod_ criteria. In our case, as the minimalSpacingPeriod_ criteria we chose the summer solstice in the Northern Hemisphere from 10 to 14 hours. We should have taken from 9 to 15, but we took from 10 to 14 to as on option of lowering the distance between the PV rows.This means that there will be no second type self-shading all year round from 10 to 14 hours.
Let me know if all of this helps in any way.…
we want to random replace 100 to 400, random replace 200 to 5, random replace 300 to 1. How could we separately control this three category inside one list?
Thank you guys so much for the help!
JJL…
reating a circle that will be divided by 200 vertical planes. Each one of these planes will contain a rectangle and by rotating these planes, we will be able to reproduce the geometry of this wooden pavilion. At some point, we will trim the bottom part of the rectangles which will represent the ground and then create surfaces from these lines which will then be extruded in normal directions for each individual plane.
➟ Project files:
https://www.patreon.com/posts/31792102
➟ Grasshopper Quick Getting Started Guide
https://howtorhino.com/grasshopper-guide
➟ Facebook group
https://www.facebook.com/groups/howto...
➟ Instagram
https://www.instagram.com/howtorhino…
Added by How to Rhino at 8:09am on November 23, 2019
ing efficiency of the script.
The basic version relies on the tutorial Nature of Code translated into Python
https://www.youtube.com/watch?v=hKHrXuSV7rE&index=13&list=PL5Up_u-XkWgPgebtPEAfck3UEPZPHBB1D
As objects are stored in the list which relies on 3 stage for loop it takes quite a while to compute more members (I am interested in up to 200). Moreover if I add external attraction to points, some separation it is even worse to that extend that estimation of computation is up to 5 minutes on my laptop with 20 members.
Please see the attached file of the basic version. It represents a specific logic that is the bases for the next steps. How to decrease necessary time to compute?
Best,
Radek…
imension(new Plane(new Point3d(5, 3, 0), Vector3d.ZAxis), new Point2d(0, 0), new Point2d(10, 10), new Point2d(5, 5));
myDim.TextHeight = 500;
doc.Objects.AddLinearDimension(myDim);
The bold line seems to be not working because I can't see any changes of text size in the rhino document.
2. I failed to add my DimStyle Object to the LinearDimension object I created above.
Rhino.DocObjects.DimensionStyle myDimStyle = new Rhino.DocObjects.DimensionStyle();
myDimStyle.ArrowLength = 100; myDimStyle.TextGap = 200; myDimStyle.TextHeight = 500;
int dimStyleIndex = doc.DimStyles.Add("myDimStyle", false);
myDim.DimensionStyleIndex = dimStyleIndex;
The bold line seems to be not changing the style of my LinearDimension object.
Could anyone help me with these two failures?
Thanks!
-Jerome
…