Documenting
Last updated
Last updated
Editing parameters for documentation follows suit with the lessons learned in prior sections. In this section, we'll look at editing parameters which don't affect the geometric properties of an element, but instead prepare a Revit file for documentation.
In the exercise below, we'll use a basic deviation from plane node to create a Revit sheet for documentation. Each panel on our parametrically defined roof structure has a different value for deviation, and we want to call out the range of values using color and by scheduling out the adaptive points to hand off to a facade consultant, engineer, or contractor.
The deviation from plane node will calculate the distance that the set of four points varies from the best-fit plane between them. This is a quick and easy way to study constructability.
Download the example file by clicking on the link below.
A full list of example files can be found in the Appendix.
Start with the Revit file for this section (or continue from the previous section). This file has an array of ETFE panels on the roof. We'll reference these panels for this exercise.
Add a Family Types node to the canvas and choose "ROOF-PANEL-4PT".
Plug this node into a Select All Elements of Family Type node to get all of the elements from Revit into Dynamo.
Query the location of adaptive points for each element with the AdaptiveComponent.Locations node.
Create a polygon from these four points with the Polygon.ByPoints node. Notice we now have an abstract version of the paneled system in Dynamo without having to import the full geometry of the Revit element.
Calculate planar deviation with the Polygon.PlaneDeviation node.
Just for kicks, like the previous exercise, let's set the aperture ratio of each panel based on its planar deviation.
Add an Element.SetParameterByName node to the canvas and connect the adaptive components to the element input. Connect a Code Block reading "Aperture Ratio" into the parameterName input.
We cannot directly connect the deviation results into the value input because we need to remap the values to the parameter range.
Using Math.RemapRange, remap the deviation values to a domain between 0.15 and 0_._45 by entering
0.15; 0.45;into the Code Block.Plug these results into the value input for Element.SetParameterByName.
Back in Revit we can kind of make sense of the change in aperture across the surface.
Zooming in, it becomes more clear that the closed panels are weighted towards the corners of the surface. The open corners are towards the top. The corners represent areas of larger deviation while bulge has minimal curvature, so this makes sense.
Setting the Aperture Ratio doesn't clearly demonstrate the deviation of panels on the roof, and we're also changing the geometry of the actual element. Suppose we just want to study the deviation from the standpoint of fabrication feasibility. It would be helpful to color the panels based on deviation range for our documentation. We can do that with the series of steps below, and in a very similar process to the steps above.
Remove the Element.SetParameterByName and its input nodes and add Element.OverrideColorInView.
Add a Color Range node to the canvas and plug into the color input of Element.OverrideColorInView. We still have to connect the deviation values to the color range in order to create the gradient.
Hovering over the value input, we can see that the values for the input must be between 0 and 1 in order to map a color to each value. We need to remap the deviation values to this range.
Using Math.RemapRange, remap the planar deviation values to a range between* 0* and 1 (note: you can use the "MapTo" node to define a source domain as well).
Plug the results into a Color Range node.
Notice our output is a range of colors instead of a range of numbers.
If you're set to Manual, hit Run. You should be able to get away with being set to Automatic from this point forward.
Back in Revit, we see a much more legible gradient which is representative of planar deviation based on our color range. But what if we want to customize the colors? Notice that the minimum deviation values are represented in red, which seems to be the opposite of what we'd expect. We want to have maximum deviation to be red, with minimum deviation represented by a calmer color. Let's go back to Dynamo and fix this.
Using a code block, add two numbers on two different lines:
0;and255;.Create a red and blue color by plugging the appropriate values into two Color.ByARGB nodes.
Create a list from these two colors.
Plug this list into the colors input of the Color Range, and watch the custom color range update.
Back in Revit, we can now make better sense of areas of maximum deviation in the corners. Remember, this node is for overriding a color in a view, so it can be really helpful if we had a particular sheet in the set of drawings which focuses on a particular type of analysis.
Selecting one ETFE panel in Revit, we see that there are four instance parameters, XYZ1, XYZ2, XYZ3, and XYZ4. These are all blank after they're created. These are text-based parameters and need values. We'll use Dynamo to write the adaptive point locations to each parameter. This helps interoperability if the geometry needs to be sent to an engineer of facade consultant.
In a sample sheet, we have a large, empty schedule. The XYZ parameters are shared parameters in the Revit file, which allows us to add them to the schedule.
Zooming in, the XYZ parameters are yet to be filled in. The first two parameters are taken care of by Revit.
To write in these values, we'll do a complex list operation. The graph itself is simple, but the concepts build heavily from the list mapping as discussed in the list chapter.
Select all the adaptive components with two nodes.
Extract the location of each point with AdaptiveComponent.Locations.
Convert these points to strings. Remember, the parameter is text-based so we need to input the correct data type.
Create a list of the four strings which define the parameters to change: XYZ1, XYZ2, XYZ3, and XYZ4.
Plug this list into the parameterName input of Element.SetParameterByName.
Connect Element.SetParameterByName into the the combinator input of List.Combine. Connect the adaptive components into list1. Connect String from Object into list2.
We are list mapping here, because we are writing four values for each element, which creates a complex data structure. The List.Combine node defines an operation one step down in the data hierarchy. This is why element and value inputs of Element.SetParameterByName are left blank. List.Combine is connecting the sublists of its inputs into the empty inputs of Element.SetParameterByName, based on the order in which they are connected.
Selecting a panel in Revit, we see now that we have string values for each parameter. Realistically, we would create a simpler format to write a point (X,Y,Z). This can be done with string operations in Dynamo, but we're bypassing that here to stay within the scope of this chapter.
A view of the sample schedule with parameters filled in.
Each ETFE panel now has the XYZ coordinates written for each adaptive point, representing the corners of each panel for fabrication.
