I generally use Dynamo for after design processes. This time we use it for an early design process and for preparation to fabrication.
Now the project is at pre-fabrication stage. We are preparing for fabrication. I will update this post later :).
I am not a coder guy, and used “BecauseWeDynamo” and “SpringNode” packages.
The next step will be using Optimo for fabrication panel optimizations.
The aim was creating a wooden interface using new methods.
We started with a mass and using dynamo packages sliced it. You can see the preparation video.
This project done at PATIKA MIMARLIK , you can see the renderings at the link.
The team was trying to build a custom pattern using notepad. This process is very hard because each time they change an element in notepad they import it in any try it again. You can see the hatch below.
Then i remember one tweet about creating hatch files with Zebra package, found it and try it.
The bad part about the hatch is the running bond changes in every 6 step, not 3.
May be you are very good at creating it with text file but its better to see the result at the background is far beyond easy.
You can import the pat file directly to the revit. It will came with correct scale.
Thanks to Zebra Package creators.
The definition file ; Hatch.
The problem was a claim came from the employer; ” All parking lots should have a number.”
First trial was collecting them with select all elements but when i put numbers it was disordered, and i remember the room numbering script along a curve.
The result was fascinating.
Group elements by values node can be found in ParametricAlly package. This node take elements and another group reference list (this list contains grouping input) and make separated groups.
In this case i collect parking lots and used levels as a references. Intersect them all with a curve, finding the start point of intersection and query the parameter At point. The result is parking lot list aligned according to the curve parameters.
After a value engineering meeting, for cost reasons, decided to lowering the level heights of the project. We have 7 model and 3 drafting file and used groups for tower levels. When you change it one by one all the groups explodes you should lower them all by once. Challenge Accepted.
This is the definition. In this work flow Ground and first floor remain the same. Basements have specific heights and upper levels heights reduced 150 mm. (that means second floor -150, third -300). And we have Architectural and Structural levels in the same file :). That definition grab the level height find its number and reduce necessary difference.
After the previous post we get a cad file containing only site points texts, no height. Points tagged manually, and non elevated. you can read heights from text. If you have dynamo you have solution. 🙂
Step 1. Select Model Elements. – Grab texts from exploded cad file. I used clockwork text element tool. Cleaned unnecessary entries.
Step 2 – Find locations with Clockwork node. Grab X and Y from location and Z from reader node.
Step 3 – Some of them share the same X.Y. and this is unacceptable for Dynamo. Sort these points along a defining curve and check X and Y values the prior and following element.