{"id":6362,"date":"2023-01-12T11:08:43","date_gmt":"2023-01-12T16:08:43","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/nx-design\/?p=6362"},"modified":"2026-03-26T04:37:36","modified_gmt":"2026-03-26T08:37:36","slug":"algorithmic-modelling","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/nx-design\/algorithmic-modelling\/","title":{"rendered":"Algorithmic Modeling | NX Tips and Tricks"},"content":{"rendered":"\n

An introduction to Algorithmic Modeling<\/h2>\n\n\n\n

Gone are the days of simplistic modeling in the world of CAD. When you combine the ever-increasing demands of the customer with the computational processing power of designers across the globe, you get the complex models we are seeing across multiple industries. Sure, products look incredible when they hit the market, but creating these models includes minute and repetitive features for functional and aesthetic purposes; usually these features are difficult to model individually using traditional CAD tools.<\/p>\n\n\n\n

What is Algorithmic Modeling?
An intuitive tool to help designers create rule-driven, complex and intricately detailed 3D models that are a true digital representation of a product in a realistic way.<\/em><\/strong><\/p>\n\n\n\n

\n\n\n\n

The importance of the Logic Editor<\/h2>\n\n\n\n
\n
\n

It\u2019s important to remember the importance of the Logic Editor within NX\u2122 software, as it plays a crucial role to allow you to author rules easily. Occasionally, complex logical rules can require several feature operations within the flowchart, i.e. the output from one operation works as the input to the next. NX Algorithmic Features excel as they do not \u2018remember\u2019 these temporary construction features that lead to the final set of output geometries. The result? An output which is as light as possible, reducing the demand from graphical and computational power, and laying the groundwork to build complex designs.<\/p>\n\n\n\n

So, with that in mind, let\u2019s look at Algorithmic Modeling within NX, and some handy tips to enhance your workflow.<\/p>\n<\/div>\n\n\n\n

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

Use Mouse Button 3 over the output port of a node in the rule window to show predicted nodes that can be selected<\/h2>\n\n\n\n

A handy trick to implement into your workflow revolves around predicted nodes. If you mouse button three over the face input port option, you will be given several commands to use to satisfy the port. At this point, you can select from different options, which are automatically added to the rule window. It\u2019s an approach which will enable you to remove the need to move between the rule window and node explorer to find the node to add your rule. Essentially, you can save a lot of time by streamlining the creation of rules.<\/p>\n\n\n\n

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

Make use of Snippets to capture key rule segments that can be saved to the Re-use Library for use in future new rule authoring<\/h2>\n\n\n\n
\n
\n

Snippets are a great way to create custom nodes, which can be re-used. There are two ways in which you can create Snippets; directly from a created group, or without the aid of a group. To do this without the aid of a group, it\u2019s a case of selecting specific nodes > mouse button three > define snippet<\/strong>. This will create a brand-new rule window that includes ONLY the nodes selected previously. All that is left to do is create an input and an output to the Snippet and save to your re-use library. It is a handy tool at your disposal, as these Snippets can be used in future projects, and by team-members to enhance collaboration.<\/p>\n<\/div>\n\n\n\n

\n

What is a Snippet?
<\/em><\/strong>The ability to capture specific segments of an Algorithmic Workflow, ready for re-use\u201d<\/strong><\/em><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n\n\n\n

Use Boolean and Separate List Nodes to optionally output construction geometry<\/h2>\n\n\n\n
\n
\n

An interesting tip we would consider implementing into your workflow is the use of Separate List nodes. Let\u2019s look at this in the context of the Spiro tube geometry, as seen in the image to the right. For this setup, two point-lists have been used, resulting in a list of lines being created. The final geometry represents the set of tubes that sit along those straight lines. With the use of Separate List nodes and utilization of True\/False, the end user is now able to see the points and lines. It\u2019s a key element to consider, particularly when working on datasets with complex shapes and structures \u2013 an architectural piece perhaps?<\/p>\n<\/div>\n<\/div>\n\n\n

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

Conclusion<\/h2>\n\n\n\n

The question is, why consider implementing any of these tips within your workflow? Well, you\u2019ll be able to build complex, repetitive, rules \u2018driven variational shapes in minutes, and add security to protect any IP captured within your rules. It\u2019s a case of easily re-using the algorithmic templates, just like you would with any other re-usable NX feature to create the complex shapes you desire.<\/p>\n\n\n\n

\n\n\n\n

Continue your journey with NX<\/h2>\n\n\n\n

Algorithmic Modeling | NX Tips and Tricks | YouTube Video<\/h3>\n\n\n\n
\n