{"id":26103,"date":"2026-02-05T23:21:12","date_gmt":"2026-02-05T23:21:12","guid":{"rendered":"http:\/\/141.23.68.248\/wp\/?page_id=26103"},"modified":"2026-02-09T22:53:09","modified_gmt":"2026-02-09T22:53:09","slug":"combined-parametric-model","status":"publish","type":"page","link":"http:\/\/141.23.68.248\/wp\/?page_id=26103","title":{"rendered":"COMBINED PARAMETRIC MODEL"},"content":{"rendered":"\n

This section presents the integrated parametric modeling of the four civil subsystems\u2014helipad, retaining wall, drainage network, and strip foundation\u2014prior to the application of the high-performance criteria HF1 and HF2. The objective of this integration stage is to establish consistent geometric, elevation, and connectivity relationships between all systems within a single Dynamo model, ensuring that changes in one subsystem automatically propagate through the others. The model captures how the helipad and concrete padding are geometrically tied to the retaining wall, how stormwater is collected and routed through gravity-driven pipes behind and below the wall, and how the foundation maintains a safe and functional spatial relationship with both the retaining wall and the drainage network.<\/p>\n\n\n\n

Integrated System Overview<\/p>\n\n\n\n

The combined parametric model integrates the four civil subsystems within a single modeling environment. All subsystems share common geometric references, including elevation levels, safety distances, and spatial offsets, allowing structural and hydraulic relationships to be defined consistently across the model. This integrated setup ensures that geometric or parametric changes in one subsystem are automatically reflected in the others, maintaining coherence at the system level<\/p>\n\n\n\n

\n
\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n<\/figure>\n\n\n\n

Figure 1:<\/strong> Overview of the integrated parametric model showing the helipad, retaining wall, drainage network, and foundation system.<\/p>\n\n\n\n

\n\n\n\n

Parametric Relationship: Helipad, Concrete Padding, and Retaining Wall<\/p>\n\n\n\n

The helipad position is defined using Point.ByCoordinates (P_Helipad_Base), which acts as the geometric reference for generating the helipad deck. The Y input of this node is connected to Code Block (sdH), which takes WallHeight+Platform and Deck.Diameter as inputs and calculates the required safety distance. This safety distance is defined as twice the retaining wall height and is required to protect the retaining wall and subsurface from vibration effects caused by helicopter operations; therefore, linking it directly to the wall height ensures that the safety requirement is always satisfied under design changes. The Z input of P_Helipad_Base is controlled by Code Block (Center.Col.Deck.Cols.Beams.Safety.PositionZ) so that the helipad elevation always follows the retaining wall and platform height, which is necessary to keep the helipad on the upper elevation of the site. The concrete padding surface is generated from the retaining wall geometry using Curve.StartPoint (RW_Start) and Curve.EndPoint (RW_End), offset with Vector.Scale (V_Depth) and created using Surface.ByPatch, because deriving the padding from the wall ensures continuous geometric and hydraulic alignment between the wall crest, the padding, and the helipad.<\/p>\n\n\n

\n
\"\"<\/a><\/figure><\/div>\n\n\n

Figure 2:<\/strong> Parametric definition of helipad safety distance and vertical positioning based on the retaining wall height.<\/p>\n\n\n

\n
\"\"<\/a><\/figure><\/div>\n\n\n

Figure 3:<\/strong> Concrete padding surface generated directly from the retaining wall geometry to maintain geometric alignment.<\/p>\n\n\n\n

Stormwater System\u2013Concrete Padding\u2013Retaining Wall Integration<\/p>\n\n\n\n

The stormwater pipe network is constructed starting from Point.ByCoordinates (PointA_Start) and extended using Point.Add with movement vectors from Vector.Scale (VectorMove_AB, VectorMove_BC, VectorMove_CE), defining the pipe layout behind the retaining wall. Slope is applied to these pipe segments by combining the horizontal movement vectors with a vertical component derived from Vector.ZAxis using Vector.Add, which is required to ensure gravity-driven flow toward the outlet rather than relying on symbolic slope values. Two stormwater inlets are positioned behind the retaining wall to collect runoff from the concrete padding, because surface water generated on the upper platform must be drained independently from the lower elevation. The elevations of these inlets are controlled by Code Block (CD_HeightDifference) and Code Block (EF_HeightDifference), which take WallHeight+Platform, PipeDiameter, and SlopeValue as inputs, ensuring that the inlet heights always remain consistent with the retaining wall height and continue to function correctly when the wall height changes.<\/p>\n\n\n

\n
\"\"<\/a><\/figure><\/div>\n\n\n

Figure 4:<\/strong> Parametric construction of stormwater pipe centerline points at the retaining wall connection.<\/p>\n\n\n\n

Stormwater System\u2013Foundation System Integration<\/p>\n\n\n\n

The foundation position is controlled by a safety distance derived from the retaining wall height and calculated using Code Block (sdF), which takes WallHeight+Platform and FoundationWidth as inputs. This safety distance is applied in the Y direction through Vector.ByCoordinates (Center of the house) and Geometry.Translate, because the foundation must maintain a minimum clearance from the retaining wall to avoid structural and geotechnical interaction. The stormwater inlet serving the foundation is positioned at the midpoint of the foundation width using BoundingBox.ByGeometry (FND_BBox) and Code Block (FND_MidY), which is necessary to ensure a stable and symmetric pipe connection even when the foundation moves. The connecting pipe segments are generated using Point.Add with Vector.Scale (VectorMove_BG, VectorMove_GH), and slope is applied using the same vector-combination logic as the upper branches, ensuring continuous gravity-driven drainage from the foundation toward the outlet.<\/p>\n\n\n

\n
\"\"<\/a><\/figure><\/div>\n\n\n

Figure 5:<\/strong> Parametric definition and validation of stormwater pipe geometry and slope for the foundation\u2013retaining wall connection.<\/p>\n\n\n\n

Final Dynamo File<\/p>\n\n\n\n

\n
Download parametric model file .dyn<\/a><\/div>\n<\/div>\n\n\n\n

Home<\/a> | Introduction<\/a> | Individual Systems<\/a> | Integration Context<\/a> | Combined Ontology<\/a> <\/p>\n","protected":false},"excerpt":{"rendered":"

This section presents the integrated parametric modeling of the four civil subsystems\u2014helipad, retaining wall, drainage network, and strip foundation\u2014prior to the application of the high-performance criteria HF1 and HF2. The objective of this integration stageContinue reading<\/a><\/p>\n","protected":false},"author":253,"featured_media":0,"parent":24786,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-26103","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/26103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/users\/253"}],"replies":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=26103"}],"version-history":[{"count":19,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/26103\/revisions"}],"predecessor-version":[{"id":29070,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/26103\/revisions\/29070"}],"up":[{"embeddable":true,"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=\/wp\/v2\/pages\/24786"}],"wp:attachment":[{"href":"http:\/\/141.23.68.248\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=26103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}